I seem to have created a problem for myself!
I have all navigations links to sections and brochure pages coded as relative paths so that I can easily upload to a test site without ending up with links that point back to the live site.
This all works fine except on secure checkout pages - when the customer enters any secure page, then decides to follow a link back out to the shopping or brochure pages - the result is that because the section or brochure links are relative, they end up looking at a normal site page via https://www.cultpens.com/...
This results in secure/nonsecure messages, plus is generally a problem - I'd prefer that they were not looking at the main pages via the secure server.
At the moment I can't see the best solution to this. Has anyone solved a similar problem or can suggest a solution?
Can it be solved using redirects (redirect all https requests except checkout to http ?); or is there a syntax method to force a relative path to go back to the nonsecure server?; should I just use https for the whole site (or is the performance hit too great?); or should I just give up on the idea?
Cheers,
simon
I have all navigations links to sections and brochure pages coded as relative paths so that I can easily upload to a test site without ending up with links that point back to the live site.
This all works fine except on secure checkout pages - when the customer enters any secure page, then decides to follow a link back out to the shopping or brochure pages - the result is that because the section or brochure links are relative, they end up looking at a normal site page via https://www.cultpens.com/...
This results in secure/nonsecure messages, plus is generally a problem - I'd prefer that they were not looking at the main pages via the secure server.
At the moment I can't see the best solution to this. Has anyone solved a similar problem or can suggest a solution?
Can it be solved using redirects (redirect all https requests except checkout to http ?); or is there a syntax method to force a relative path to go back to the nonsecure server?; should I just use https for the whole site (or is the performance hit too great?); or should I just give up on the idea?
Cheers,
simon