We used to have two domain names one was for consumers and the other for B2B. We consolidated them and in all but one scenario the redirect occurs. Below is the list of the various ways I have checked the redirect:
http://old-domain.com (Redirects-fine)
http://www.old-domain.com (Redirects-fine)
https://www.old-domain.com
https://old-domain.com (problem)
I used IIS to create the redirect by creating a new website and then pointing to the same directory and then on the home directory tab of IIS "A redirection to a URL" with http://www.new-domain.com$
Thanks,
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>>I used IIS to create the redirect by creating a new website
does that new web site have ssl enabled? it will need a cert installed, and it will need to be listening on port 443.
what happens when you do access it with https://www.old-domain.com
Cheers.
Yes the site has an SSL for the new site name not the old. when you try to access the www.old-domain.com you get a cert error, which should happen. But what we are trying to accomplish is the following: there are links out on the web that contain https://old-domain.com which will bring up the ssl error. Is there a way to redirect that https://old-domain.com to the current website of https://hcibooks.com
Hi,
so you want to prevent the error from showing up when they hit 'https://old-domain.com'?
In that case you need to make 'old-domain.com' point to a different IP address and set up the ssl web site with VALID cert for 'old-domain.com', and enable the redirection like you did already.
This behaviour is happening because the ssl connection must be established before the web server can issue the redirect instruction - and so it must go through all the usual ssl step-up processes including check of the cert.
Cheers!
Mike.
Hi,
same server is OK - so long as you have an independent IP address and valid cert, it doesn't matter if it is on the same server or not.
A wildcard certificate will do the job to cover you for both http://www.old-domain.com and http://old-domain.com
Cheers!
Business Accounts
Answer for Membership
by: tedbillyPosted on 2009-06-11 at 21:25:50ID: 24609116
Why the redirect? Has the site structure changed? If not, then why not just add the DNS names to the web application with the existing domain names?