Forum Discussion
irule prepend www to https request
Hi, SSL client processing takes place before HTTP_REQUEST is fired (as until SSL is complete, TMM cannot read the request details).
The browsers do all behave slightly differently (and between versions), but in general when you click OK in the browser to view the page you are essentially caching that cert for the mismatching domain for the duration of the browser session - I don't think that clearing cache removes it - you need to close either that window or all windows to get rid of the caching.
If you need your site to perform a redirect from https://test.mydomain.com to https://www.test.mydomain.com then you will need to include the test.mydomain.com FQDN as a Subject Alternative Name in your certificate, otherwise users will get the cert error.
- GeorgeA_32263Feb 24, 2014
Nimbostratus
IheartF5: I greatly appreciate your explanation. Now things make sense. Thank you.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com