: Secure Image is being called Insecure? I have an image using the secure protocol (https://) but the image is being called insecurely from our homepage using the protocol (http://) - How is this
I have an image using the secure protocol (https://) but the image is being called insecurely from our homepage using the protocol (http://) - How is this possible? Our SSL Certificate is installed correctly & our Secure Padlock Icon will not show because of this. Thank you!
(Secure) As found in the source code: shopcandelabra.com/skin/frontend/default/candelabra/images/virtualtour.jpg
(Insecure) What the homepage is calling: shopcandelabra.com/skin/frontend/default/candelabra/images/virtualtour.jpg
More posts by @Hamm4606531
1 Comments
Sorted by latest first Latest Oldest Best
301 Redirect
Appears your image file has a 301 redirect. So the browser will load the HTTP version while the code says HTTPS.
curl -I www.shopcandelabra.com/skin/frontend/default/candelabra/images/virtualtour.jpg HTTP/1.1 301 Moved Permanently
Date: Wed, 09 Jul 2014 16:12:53 GMT
Server: LiteSpeed
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
Location: shopcandelabra.com/skin/frontend/default/candelabra/images/virtualtour.jpg Vary: User-Agent
You will want to inspect any rewrite rules that could be triggering this.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.