Why would leaving www from a URL affect the routing and certificate validity
Entering http://www.felixstowerotaryclub.org correctly routes to the correct website and sets up a secure connection.
Entering http://felixstowerotaryclub.org routes back to the old website.
Entering https://www.felixstowerotaryclub.org connects correctly
Entering https://felixstowerotaryclub.org gives an invalid certificate error.
How can I get http://felixstowerotaryclub.org to route to the new website and https://felixstowerotaryclub.org to not give an invalid certificate error?
Entering http://felixstowerotaryclub.org routes back to the old website.
Entering https://www.felixstowerotaryclub.org connects correctly
Entering https://felixstowerotaryclub.org gives an invalid certificate error.
How can I get http://felixstowerotaryclub.org to route to the new website and https://felixstowerotaryclub.org to not give an invalid certificate error?
Scott Fell
Your best option is to use only the www and instead redirect the naked domain to www. This would be true with or without using a cert for seo reasons.
ASKER
I wouldn't say it was the best option to force people to have to enter "www" - it seems pretty common nowadays for people to not have to always add it in - how would it normally work to make it optional?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Suggestion: Might be useful for you to hire someone for an hour or two, to go through your entire setup to work through all details, so you have a rock solid starting point.
ASKER
Thanks I'm sure that's enough to get me sorted! Much appreciated.
You're welcome!
Glad you have clues toward a resolution!
Glad you have clues toward a resolution!
I wouldn't say it was the best option to force people to have to enter "www" -Your right, it is not. On your server the proper thing to do is set up a redirect as David points out. If somebody surfs (actually 'Cerfs') to the naked domain, you will set up a redirect to the 'www'. That way no matter if they go to the naked domain or www, they end up at the www where you have a certificate.
I use wildcard domains but that is for using sub domains such as dev.mydomain.com along with www.mydomain.com. For live content, I always redirect to either the www or naked, typically the www but not allow both.
I hope that makes sense.
ASKER
Yes sorry Scott I misunderstood your original comment - your suggestion does sound very sensible.