Oracle Payments Call To Oramipp Servlet Is HTTP 1.0 Instead Of HTTP 1.1 (Doc ID 1504801.1)

Last updated on JULY 17, 2024

Applies to:

Goal

Our web service provides credit card authorization and settlement routines in a multi-tenant (multiple customer) environment. This approach relies on extracting the host name (Host: header) from the request URL within the HTTP environment to determine the “customer” or client for each request.

Additionally, this service is implemented as Payments “Gateway” payment system. When Payments invokes the URL corresponding to a call (from Oracle EBS r12 Payments module) to the gateway payment system, it does so in accordance to HTTP/1.0 specifications. However, HTTP/1.0 does not enforce the inclusion of a Host: header. It is therefore optional. We have resorted to hard-coding the hostname and running multiple copies of the application on our hosted site.

If the invocation was HTTP/1.1 and/or included the Host: header, no hard-coding would be necessary and we could run a single, multi-tenant version of the software.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.