SSL Errors when redirecting from HTTPS://mysite.com to HTTPS://WWW.mysite.com
I have a site with SSL enabled and the SSL certificate is registered to www.mysite.com (example). I have set up all the appropriate redirects to force all traffic to include www and ssl. If a person types in http://mysite.com they are successfully redirected to https://www.mysite.com. If a person types in http://www.mysite.com they are successfully redirected to https://www.mysite.com. HOWEVER, if a person types in https://mysite.com they ARE NOT redirected to https://www.mysite.com and they receive an error message that the site is insecure because the name does not match the certificate.
This all works in other browsers (eg. Google Chrome, Opera) but it fails in Firefox. Anyone know how to fix this without paying for a new certificate (this certificate is only 2 months old and is registered for 2 years)?
The rules in the .htaccess file are:
RewriteEngine On RewriteCond %{HTTP_HOST} ^mysite\.com [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.mysite.com/$1 [R,L]
所有回复 (5)
Fix your code to W3C.org standards and practices and future development of web page code and Web Browsers. The people in Charge. Just because the other browsers see bad code does not mean Firefox and 20 more others will like not Google will iike it.
HTML ERRORS on the HTTP site :
CSS No Errors on HTTP site :
W3C.org Who make the rules for web code.
HTML https://validator.w3.org/ CSS https://jigsaw.w3.org/css-validator/ and https://validator.w3.org/i18n-checker/ and http://mobile.css-validator.org/
Please let us know if this solved your issue or if need further assistance.
I'm sorry but I thought I was very clear that the URL "www.mysite.com" was just an example URL rather than the actual URL. Therefore, code validation against an invalid site URL that was only used as an example are not accurate and not helpful. This is not a code issue this is an issue with how the browser is handling URL REWRITES with the .htaccess file PRIOR to even attempting to load code.
Thank you for attempting to answer.
cysurfer said
I'm sorry but I thought I was very clear that the URL "www.mysite.com" was just an example URL rather than the actual URL. Therefore, code validation against an invalid site URL that was only used as an example are not accurate and not helpful. This is not a code issue this is an issue with how the browser is handling URL REWRITES with the .htaccess file PRIOR to even attempting to load code. Thank you for attempting to answer.
Sorry, maybe should wear my glasses more often. I find nothing on ver 57. As usual clear cache, cookies and check again. Did find this site, no idea if any good or not :
I definitely understand the need for glasses. I have that issue myself. Yes, I've done all the normal stuff of clearing cache, restarting the browser and computer. I've even asked other people to try it and it is a problem on Firefox every time. The weird thing is that all other redirect TS work fine in Firefox. The only one that does not work is if the user uses httpS and the domain name without a he www. If they use http without the www, it redirects correctly.
Normally issuers cover both domain.tld and www.domain.tld in the same certificate, so it's surprising that yours did not. Hopefully you can get the certificate replaced at no additional charge.