Link to home
Start Free TrialLog in
Avatar of webmonkey8
webmonkey8

asked on

How do I redirect http to https in IIS 6?

I have many websites hosted on my IIS 6 Windows 2003 server and I've just implemented a SSL certificate for one of the websites successfully. The only problem is that when users connect to the "old" site via http, they're getting another website residing on my server.  

Is there a way to:
1) redirect users somehow accessing http://myURL.com to https://myURL.com easily?
2) fix why users get directed to another website residing in on my server by going to http://myURL to http://someotherURL.com?

One more note, the fact that users are receiving another website residing on my server has to do with caching from the proxy server which I cannot resolve.  

Thanks.
Avatar of warturtle
warturtle
Flag of United Kingdom of Great Britain and Northern Ireland image

Have a look at this:

http://blog.opsan.com/archive/2005/04/17/395.aspx

You must write an error page for HTTP error 403.4 (SSL required) error and that should redirect to http://myURL. That will resolve the issue for you.

Warturtle
oops, i meant that should redirect to https://myURL.com

Avatar of webmonkey8
webmonkey8

ASKER

warturtle - thanks for the info.  However, when accessing http, I do not get a 403.4 error, instead, I'm receiving another website residing on my server.  

I'm not too sure why http://myURL.com is going to my other site, whereas https://myURL.com goes to the right one.  

Is there something in IIS 6 that needs to be changed?  I did notice that in the website that http is going to, the "Advanced Web Site Identification" section, there are 3 "Multiple identities for this Web site":
1) IP address,  TCP port of 80, www.myURL.com
2) Default, TCP port of 80, myURL.com
3) Default, TCP port 80, (empty entry)

If you have an idea of what's going on, I'd appreciate it!  thank you.
thanks, warturtle. However, after reading those articles, I'm still at a loss as to what exactly I need to do in my situation.  As going to http://myURL.com goes to another website, instead of a 403.4 error is strange.  
Please advise.  Thanks.
Hello,

Can you please check your windows hosts file to make sure that there is no duplicate entries or if www.myURL.com has the same IP address as www.someotherurl.com. This could be causing the problems. It could be that IIS is trying to serve the correct website but the settings within IIS are overriden by the settings within the windows host file. It seems to be a DNS problem, for all I understand. For ex-

10.10.10.10 www.myurl.com
10.10.10.10 www.someotherurl.com

This would cause problems and if the website myurl.com is marked as Default, then it will always redirect users to that if someone types in 10.10.10.10. Let me know, if you see any strange entries within the hosts file.

Warturtle
There are about 15 websites on the IIS and they all have the same IP in the "Multiple identities for this Web site" field.  When going to each site, they go to their respective location.  However, when I implemented a SSL certificate for one of the websites, I start receiving what I have mentioned in my previous posts.  But yes, there are duplicate entries but I'm not too sure if I should delete the duplicate ones as all sites are live.

Also, when I installed another SSL certificate on the 2nd website, it automatically stops the website. When I click on start in IIS manager, it says:

 "IIS was unable to start the site.  Another site may already be using the port you configured for this site.  Please select a unused port for this site".

I'm not too sure what to do here as I already have one website successfully setup in SSL (https), however the "http" is referencing another site.  
ASKER CERTIFIED SOLUTION
Avatar of warturtle
warturtle
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks warturtle, you have been most helpful!  I'm going to register another IP for my other SSL website.  However, you've mentioned that I can also assign different port numbers, instead.  Do different port number need to be registered as well?
Yes, different port numbers can also be used, they don't need to be registered though. Its just that you have to open that port in your firewall and users will have to use it in the URL as well, for ex - http://www.myurl2.com:288888 will take you to myurl2 website. Its not recommended for production environments though. More info on the below link:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/883a9544-3f70-4d46-a6df-bbadbd1fe7de.mspx?mfr=true

Always happy to help.
Excellent help from 'warturtle'!