karamba
12 years agoNew Contributor
WSDL location doesn't handle reverse proxy headers
Hello,
I'm using a webservice in backend (on an apache tomcat http server) and in frontend, a apache reverse proxy in https.
When requesting for the wsdl, i'm getting location with "non-https" value.
I dumped tcp on the reverse proxy, and i see that i'm sending the good headers :
However, i'm getting the wsdl xml, but not the good "location" including https :
<soap:address location="http://reverseproxy-fqdn:80/WebService" />
instead of
<soap:address location="https://reverseproxy-fqdn/WebService" />
Is there specific settings to put on the webservice using soapui to handle correctly the headers please?
Regards,
I'm using a webservice in backend (on an apache tomcat http server) and in frontend, a apache reverse proxy in https.
When requesting for the wsdl, i'm getting location with "non-https" value.
I dumped tcp on the reverse proxy, and i see that i'm sending the good headers :
[b]X-Forwarded-proto: https\r\n
Front-End-Https: On\r\n[/b]
X-Forwarded-for: CLIENT-IP\r\n
X-Forwarded-Host: REVERSEPROXY-FQDN\r\n
X-Forwarded-Server: SERVERNAME\r\n
Connection: Keep-Alive\r\n
\r\n
[Full request URI: http://reverseproxy-fqdn/WebService?wsdl]
However, i'm getting the wsdl xml, but not the good "location" including https :
<soap:address location="http://reverseproxy-fqdn:80/WebService" />
instead of
<soap:address location="https://reverseproxy-fqdn/WebService" />
Is there specific settings to put on the webservice using soapui to handle correctly the headers please?
Regards,