Forceing https on http web pages.

Right, but that could actually be multiple things. The Redirect Rewrite option in the HTTP profile will catch 30x redirect responses from the server and replace http:// with But then you may also have to deal with:

1. Internal URLs - the server may be responding with absolute URLs (ex. the VIP FQDN is https://www.example.com but the server is sending back references to

    

2. Payload content - The Location header is usually the only HTTP response header that will have a URL, but the payload - the actual HTML content of the response - can have URLs anywhere. Every document object that an HTML page references will have a URL. That URL may be relative (ex. /images/my-cat.png) or absolute (ex. If the server is sending these URLs back through to the client, your internal clients may just be able to access these directly (around the BIG-IP), but external clients will not.

    

The important thing here is to understand what's happening. There are a number of things you can do to rewrite response URLs, but you need to know what the problem is first. The best way to do that is with a client side HTTP capture utility like Fiddler or HTTPWatch. These tools will show you, form the browser's perspective, what the client is sending and how the server is responding. If you're actually getting internal URLs in the response payload, you'll see the browser attempting (and failing) to access these URLs.