For a web application located at:
With an SSL certificate issued to “www.domain.com”,
What is are the proper rewrite rules, DNS settings, or combination of both which makes each of the below urls redirect seemlessly to
1. http://www.domain.com 2. http://domain.com 3. https://domain.com
The difficulty is really with #3.
https://domain.com tends to cause browser security messages. How do the major HTTPS sites do this? Take Paypal.com, for instance.
As some more assistance for item 3, and maybe 2 as well, how about using Server Name Indication to use two certs on the same host. (ie: www.domain.com and domain.com) Apache’s Wiki has some info on the specifics.
- Apache rewrite rules behind a nginx proxy
- Apache module “mod_jk”. Setup rewrite condition for using https for specific url/context
- domain not getting resolved without www. Despite appropriate apache settings and DNS records
- Why do some rewrite rules fail while AJP is serving all of my requests to Tomcat?
- Apache server rewrite rules: how to avoid “implicitly forcing redirect (rc=302)”?
Leave a comment
- What is the easiest way to upgrade my existing Perl 5.14 to Perl 5.16 on FreeBSD 9 using the ports system?
- Know if mysql has done its job
- Redirect https .com to https .co.uk without a valid SSL cert on .com without DNS change
- Why is it a bad idea to use customer email as from address
- 100% packets dropped on first RX queue on 3/5 raid6 iSCSI NAS devices using intel igb (resolved)