Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

.htaccess redirect from www to non-www not working in Firefox?

more options

.htaccess redirect

RewriteCond %{HTTP_HOST} ^www\.ice\-warrior\.com$ RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$ RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$ RewriteRule ^/?$ "https\:\/\/ice\-warrior\.com\/" [R=301,L]

Not working in Firefox - works on all other browsers. SHould redirect https://www.ice-warrior.com to https://ice-warrior.com

.htaccess redirect RewriteCond %{HTTP_HOST} ^www\.ice\-warrior\.com$ RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$ RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$ RewriteRule ^/?$ "https\:\/\/ice\-warrior\.com\/" [R=301,L] Not working in Firefox - works on all other browsers. SHould redirect https://www.ice-warrior.com to https://ice-warrior.com

모든 댓글 (2)

more options

You could try empty your cache and delete cookies for site/s That has worked in the past. Not sure how google likes it but you can place in the <head> a <meta http-equiv=</> to redirect to the page or a 302 Redirect Have you checked with the server support team and also looked at the .htaccess file to see if corrupted ?

Is this something new you are setting up or is this a existing site that worked before any Firefox updates ?

글쓴이 Shadow110 수정일시

more options

I get:

Your connection is not secure

[Advanced panel]

www.ice-warrior.com uses an invalid security certificate. The certificate is only valid for the following names: earth-warrior.com, ice-warrior.com Error code: SSL_ERROR_BAD_CERT_DOMAIN

So in that case, because there's no connection, Firefox does not get the redirect. Neither does Internet Explorer 11. (I'm curious why Chrome doesn't have this issue; they may have some special workaround for this situation?)

It's a little odd because Comodo usually gives you both the base domain and the www subdomain. Not sure if they'll "fix it for free" or whether you need some kind of Plan B to resolve this.