Show Posts
1
Support / Re: Mixed Content Errors with SSL Termination via nginx to Varnish cache
« on: January 29, 2016, 10:56:24 PM »
I have now performed a complete system reinstallation using the instructions available on this forum. While the installation was a success, it did not resolve my HTTPS problems.
It is odd to me that the site has not switched to HTTPS since I have had other sites use AbanteCart's SSL feature successfully. I have noticed that it appears that only a series of image files are not being loaded (though it certainly looks as if it's missing css), though the navigation links are written in http;// and therefore not functioning properly.
@eCommerce Core:
My version is the latest, 1.2.5.
I think you're brilliant of your observation of contained HTML. I think this may explain some discrpencies between http and https, though it does not account for the css break.
@abolabo
I checked where you talked about, indeed in fact the whole options, though I cannot find another options related to SSL/TLS.
Thank you for the recommendation for Google Pagespeed. I love and use it, along with the ModPagespeed to tidy up with minification, concatenating, and caching, though it is presently turned "unplugged" so there seem to be lots of improvements.
My best hypothesis at the moment is that since some of the content is served via Varnish on port 80, it is detecting this (or, based on the code, failing to be excepted) as HTTP. In turn, some things are being built with the HTTP links. My only issue with this theory is that manually setting the HTTPS variables do no elicit the appropriate response.
Thank you for your continued efforts!
It is odd to me that the site has not switched to HTTPS since I have had other sites use AbanteCart's SSL feature successfully. I have noticed that it appears that only a series of image files are not being loaded (though it certainly looks as if it's missing css), though the navigation links are written in http;// and therefore not functioning properly.
@eCommerce Core:
My version is the latest, 1.2.5.
I think you're brilliant of your observation of contained HTML. I think this may explain some discrpencies between http and https, though it does not account for the css break.
@abolabo
I checked where you talked about, indeed in fact the whole options, though I cannot find another options related to SSL/TLS.
Thank you for the recommendation for Google Pagespeed. I love and use it, along with the ModPagespeed to tidy up with minification, concatenating, and caching, though it is presently turned "unplugged" so there seem to be lots of improvements.
My best hypothesis at the moment is that since some of the content is served via Varnish on port 80, it is detecting this (or, based on the code, failing to be excepted) as HTTP. In turn, some things are being built with the HTTP links. My only issue with this theory is that manually setting the HTTPS variables do no elicit the appropriate response.
Thank you for your continued efforts!