Forum Moderators: phranque

Message Too Old, No Replies

https redirection old.com to new.net

ssl issue

         

ItsR

6:50 am on Dec 20, 2014 (gmt 0)

10+ Year Member



Hello,

We are moving old domain to new domain. example.com to example.net

Created DNS records and Rewrite rules in apache configuration.

http://www.example.com to [example.net...] redirecting perfectly.

[example.com...] redirecting shows Connection Untrusted

www.example.com uses an invalid certificate
The certificate only valid for the following names:
www.example.net , example.net
(Error code:ssl_error_bad_cert_domain)

Please suggest me how to resolves.

Regards,
ItsR

[edited by: phranque at 8:37 am (utc) on Dec 20, 2014]
[edit reason] exemplified domains [/edit]

phranque

8:44 am on Dec 20, 2014 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



welcome to WebmasterWorld, ItsR!


there is likely a problem with the secure certificate for www.example.com

lucy24

8:57 am on Dec 20, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



https://www.example.com redirecting shows Connection Untrusted

Do you mean that the redirect doesn't take place at all? Or that the browser puts up a warning? Or just that your logs note the error somewhere in the background? Does it apply to all requests for the old site, or only selected URLs or methods?

Interesting issue in any case. The mere act of requesting an https page triggers a search for a security certificate, even if the page itself will never be served up.

I assume there's some reason you can't simply apply a certificate to the old domain. Is the security certificate for example.net (the new site) a brand-new one, or did you change the existing certificate's info from old domain name to new?

ItsR

9:39 am on Dec 20, 2014 (gmt 0)

10+ Year Member



Hi,

https Redirection takes place after adding exception.

SSL certificate for example.net is brand new.

SSL Certificate of example.com is valid.

Please let me know if need more information.

Thanks

phranque

9:39 am on Dec 20, 2014 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Interesting issue in any case. The mere act of requesting an https page triggers a search for a security certificate, even if the page itself will never be served up.


the secure handshake occurs before the web connection is made.
the browser will trust a legit certificate.
since the connection isn't properly secured or identified, the browser requires permission from the visitor to proceed.

ItsR

9:45 am on Dec 20, 2014 (gmt 0)

10+ Year Member




How to resolve this? Is it normal issue when https redirection takes place from domain example.com to example.net

Any suggestion to fix this issue.

lucy24

8:12 pm on Dec 20, 2014 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



SSL Certificate of example.com is valid.

If you remove the redirect, do requests for example.com go through? (If this is a live site, you could test it by coding one exception to the redirect, and requesting that specific URL. It can even be a made-up URL.)

Double-check: All requests, all the time? GET or POST, with or without parameters? Do the two domains live on the same server?

Obviously something has gone wrong on the technical end; we need to figure out where the problem is happening.

phranque

10:40 pm on Dec 20, 2014 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



SSL Certificate of example.com is valid.


what about the certificate for www.example.com ?

https://www.example.com redirecting shows Connection Untrusted


what happens to requests for [example.com...] ?