We are implementing a scenario where a third party web application in the public domain sends a soap-call to the ECC backend directly, i.e. without using a middleware such as PI.
In the DMZ is an Apache reverse proxy who receives the encrypted call from the website, and sends it decrypted to the backend.
The website sends the message to an IP-address corresponding with the reverse proxy server, and putting a (non-hosted, made up) host name in in the soap header.
The reverse proxy reads the header, and, depending on the value in the host-tag, redirects the message to the appropriate backend server (development, acceptance or production).
We see incoming traffic in ECC's ICM, but ECC immediately responds with an HTTP:404 error.
In the message that the reverse proxy sends we read the following:
POST / HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://<namespace>/<interface>/<operation>"
host: https://<non-hosted-ip-address>
location: https://<internal-sap-server-id>:<dito-port>/sap/bc/srt/xip/sap/<service-definition>/<client>/<configuration-soamanager>/binding
Content-Length: xxx
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Why is the address empty in the POST method? Does it matter? If so, who is to set the address in the POST method? Is it the reverse proxy when relaying the message? Or am I missing some configuration in the SAP backend.