deepee Posted February 27, 2015 Share Posted February 27, 2015 (edited) Hi All I just noticed this on my 1.5.6.2 shop after enabling SSL for all pages. Firefox gives the mixed content warning and turning on the web consol I see the code is trying to load my product images from HTTP:"Loading mixed (insecure) display content on a secure page "http://mysite.com/1196/thing.jpg GET http://mysite.com/1196/thing.jpg" Anywhere I can change this? Thanks deepee Edited July 28, 2015 by deepee (see edit history) Link to comment Share on other sites More sharing options...
tomerg3 Posted February 27, 2015 Share Posted February 27, 2015 Link to comment Share on other sites More sharing options...
deepee Posted February 28, 2015 Author Share Posted February 28, 2015 Not sure what you mean tomerg3? Link to comment Share on other sites More sharing options...
deepee Posted March 4, 2015 Author Share Posted March 4, 2015 In the absence of any replies I searched the forums again and found one suggestion to disable and then re-enable friendly URL's. I tried it but it threw the same warning with friendly URL's switched off. I re-enabled friedly URL's and tried it in Chrome but get the same errors as in Firefox, e.g. :- Mixed Content: The page at 'https://mysite.com/some-category/312-some-product.html' was loaded over HTTPS, but requested an insecure image 'http://mysite.com/1080/thing.jpg'. This content should also be served over HTTPS. I'm stumped... Anyone? Link to comment Share on other sites More sharing options...
tomerg3 Posted March 4, 2015 Share Posted March 4, 2015 Check what is generating the http link, and fix it. Link to comment Share on other sites More sharing options...
deepee Posted March 4, 2015 Author Share Posted March 4, 2015 (edited) If I knew how to do that I wouldn't be asking the question here tomerg3. Your first reply to my post was empty except for an advertisment for your own webshop and then this cryptic response? Not what I would expect from a senior moderator and certainly not one who is trying to peddle their own modules to the community. Edited March 4, 2015 by deepee (see edit history) Link to comment Share on other sites More sharing options...
tomerg3 Posted March 4, 2015 Share Posted March 4, 2015 Seems like the forum is a bit buggy when trying to type http followed by a colon and two slashes Based on your cryptic message, I gave the best answer I could... View the source of the page, and find what's using the wrong link, I doubt it's a product image, but as you didn't post a URL, there's no way to check.... Link to comment Share on other sites More sharing options...
deepee Posted March 5, 2015 Author Share Posted March 5, 2015 The question wasn't meant to be cryptic, tomerg3. The problem is that every post to this forum is indexed by the search engines. It means that each time a real URL is posted, it is indexed and will turn up in search queries relating to that domain. Doesn't look great when customers are searching for something relevant to that domain only to see a load of posts about technical issues about the website they are buying from. I have no issues sending real URL details in a PM. My example is exactly what happens on the live site. Every other image element that is generated on any product page is behind https, e.g. https://mysite.com/1080-large_default/thing.jpg However, the original product image from which the image elements are built is still being called from http. That's the only thing that triggers the mixed content warning. Link to comment Share on other sites More sharing options...
tomerg3 Posted March 5, 2015 Share Posted March 5, 2015 IF you are worried about the URL, post it with hyphens, or spaced out, that way other members can help as well. Without it, all I can suggest is check the product.tpl file, specifically for the main product image link Link to comment Share on other sites More sharing options...
xnettoc Posted March 22, 2015 Share Posted March 22, 2015 Hi, I have the same problem. Some images are being served by http insted of https. I wouldn't want to edit source code. I don't know if any way to solve by .htaccess or anyway. Thanks Link to comment Share on other sites More sharing options...
deepee Posted July 28, 2015 Author Share Posted July 28, 2015 I upgraded to version 1.6.1.0 and this issue has disappeared so marking as solved. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now