Secure Site not working correctly

Hi Angelo,

 

 

It sounds like the application is referencing itself over HTTP when being SSL proxied by LTM. If you want to avoid the client getting an insecure content warning, you'd want to rewrite the response headers and/or payload from http:// to https://. It would help to determine where the http:// reference is (in response headers and/or content). You can use a browser plugin like HttpFox for Firefox or Fiddler.

 

 

Depending on the application, you might be able to configure it to reference itself using https://. If not, you should be able to use an iRule to rewrite the http:// references to https://.

 

 

Aaron