Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Forcing HTTP 1.0 or 1.1 for incoming calls to the Axway/Vordel API Server

DZone's Guide to

Forcing HTTP 1.0 or 1.1 for incoming calls to the Axway/Vordel API Server

· Integration Zone ·
Free Resource

SnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.

In a previous post, I wrote about how you'd configure the Axway/Vordel API Server to connectout to APIs using either HTTP 1.0 or 1.1. But, what if you wanted to force the API Server to receive API calls using either HTTP 1.0 or 1.1? This can be done using a simple trick. What you do is to create an "incoming" Remote Host, as shown below. In the example below, I've checked the box for "Force HTTP 1.0". This forces incoming connections to use HTTP 1.0

With SnapLogic’s integration platform you can save millions of dollars, increase integrator productivity by 5X, and reduce integration time to value by 90%. Sign up for our risk-free 30-day trial!

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}