lucy24 - 9:41 am on Jul 5, 2013 (gmt 0)
Will not that overwrite the shopping cart secure URLs with https:// to http:// as well?
No. Any given URL should be accessible by either https or http but not both. If you're lucky, the secure and non-secure pages live in different folders, making the rules easier to construct.
I don't speak IIS so I don't know what the mechanics are. But all the user sees is a 200 or a 301, no matter how you arrive there.
And then you've got the problem of non-page content like pictures and stylesheets. There's no intrinsic reason for them to be secure-- but browsers tend to make alarming noises if the user isn't getting a matched set. ("You have requested a secure page that includes some non-secure content.")
So far, I don't think g### has started making a fuss about Duplicate Content when it discovers that
is exactly the same as
So you can back-burner the Non-Page issue and just get your pages sorted. No, the solution does not have to involve hard-coding all links in html. Brr.