We allow people to connect to the site with `example.org` or
`www.example.org`. For the area where we do checkout we are forcing the
https via PHP but if they came into the page from `example.org` there is a
warning since our certificate is signed with the `www.example.org` domain.
Is their a good rewrite rule out there I could use. I've tried a few I found
but there weren't working 100%.
The solution to this is actually partly redirecting and partly virtual
hosting. When I've got a site that has more than one URL that will work,
I usually think long and hard about which URL should show in the browser
and almost always make it so they are sent to that URL from all the
others that will resolve to the site.
That way, you can produce as much ad copy as you want, using the
shortened name (even for deep links), and anyone who goes to the site
with the short version is automatically sent to the correct location
using the full version of the domain name.
-Brian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Web-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/web-dev/email@hidden
