Hi,
We have deployed Web Application Proxy in our DMZ to publish some services to the internet. This works fine with all our services except for one. This service responds with a redirect :
HTTP/1.1 302 FoundServer: Apache-Coyote/1.1
Cache-Control: no-store, no-cache
Pragma: no-cache
Expires: Tue, 05 Aug 2014 07:32:32 GMT
X-UA-Compatible: IE=Edge
Set-Cookie: JSESSIONID=D31478B944B1AF3331566EBFB03E4162; Path=/<serivce>/; HttpOnly
Location: http://<internal-serveraddress>:8080/<service>/login.do;jsessionid=D31478B944B1AF3331566EBFB03E4162
Content-Type: text/html;charset=UTF-8
Content-Length: 0
Date: Wed, 09 Sep 2015 07:32:32 GMT
This redirect is passed through the proxy to the client on the outside. The problem is that the WAP server URLEncodes the Location and Set-Cookie response. So that the client tries to reach the following address when it responds to the redirect response :
https://<extranal server>/<service>/login.do%3Bjsessionid%3DD31478B944B1AF3331566EBFB03E4162
This address is not a valid URL for the web server.
As far as I can tell this look like a bug in the WAP server, or is this someting that could be configured to behave differently ?.
/Trond Tunheim