Rewriting HTTP redirection with HTTPS->HTTPS (SSL-to-Server feature) does not func.

Thanks for the information.

 

 

But we already tried the "Rewriting HTTP redirecct" option for the SSL proxy configuration (Big-IP Vers. 4.6.2).

 

 

Unfort. we had no luck to get it work.

 

 

Maybe it has something to do with ->, that the SSL proxy is not able to do the "rewrite redirect" for SSL (HTTPS) delivered responses. We tried it in many ways, but the "LOCATION" header has always been delivered to the client with the WebSphere Appserver port information and port was not "stripped out" as it should with the "rewriting HTTP reditrect" option enabled.

 

 

The doccumentation, concerning the "Rewriting HTTP redirection", is only talking about redirects for:

 

 

1.) Incoming HTTPS traffic which flows to appserver as HTTP, and resulting HTTP response would be redirect as HTTPS to the client.

 

 

Question:

 

Can the same work for HTTPS <-> HTTPS - only stripping out the port information inserted by the appserver (..or could it not work by design)?

 

 

Can somebody give an example of an working example configuration (Steps for SSL-Proxy, virt. Server/IP, HTTPS Pool)?

 

 

Any thoughts are very welcome :-)

 

 

Best regards,

 

Jan