Msg#: 4421660 posted 11:51 am on Feb 25, 2012 (gmt 0)
I have two issues that maybe an expert out there can help me with:
1. I start making an enquiry, the final page has to be on the secure server. That works ok, but, when I click on one of the Pages, the page tries to go to the https version even though the Permalink is set to go to the http. Can I change this action?
2. When I get to the https version the browser comes up with the error message saying that there is non-secure items being displayed also (I guess that these are the images). How can I get around this error message?
Msg#: 4421660 posted 1:06 pm on Feb 26, 2012 (gmt 0)
Sorry for the delay.
The system I'm using is to get a quote. When the customer finds my website, naturally they're on the http:// when they make an enquiry and get a list of products displayed they're switched to https:// as, when they select their product, they're prompted for their credit card details (this is controlled by the company that provides the quotation softare).
When on http:// the page links (Contact Us, FAQ etc) are pointing to [,...] when the customer makes his enquiry and goes to https:// then all the links to the pages also switch to https://. I'd rather that they stay pointing to [....]
When I check the Permalink for each Page it says http:// but when the customer lands on https:// the links switch to https://.
Msg#: 4421660 posted 4:14 pm on Feb 26, 2012 (gmt 0)
If the links within the page are not absolute urls, the http:// will change to https://.
If you are running .php or .asp pages, you can put a script in the other pages to switch them back to [,...] though I would assume there is probably a script to cause the links on your https:// to change to [,...] but I am not aware of one.
As for the mixed content message, if the image is hosted on your server and uses a relative path, that should not cause a problem. If you have any thing fed from outside such as images or scripts, that could be your problem. Also if you use Rich Snippets and have an image in the itemprop="img" content="http://IMAGE URL", that would also cause a mixed content notice.