AbanteCart Community
Shopping Cart Operations => Support => General Support => Topic started by: shahiran12395 on September 25, 2019, 11:23:17 PM
-
hi, im having trouble with Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint '<URL>'. This request has been blocked; the content must be served over HTTPS.
how can i solve it?
-
Hello.
You have few options. First you can change urls for your content to https://, also can set a rule in your htaccess file to redirect all http to https if content on your website
-
i have try using htaccess but nothing change and i using the default abantecart so how can i edit it to https? the mixed error msg is
Mixed Content: The page at 'https://{URL}' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://{URL}/index.php?rt=r/product/product/addToCart'. This request has been blocked; the content must be served over HTTPS.
-
Did you enable SSL in your AbanteCart store settings?
-
i already do it. but still cant got the error. if disable https everything work fine.
-
have you made any changes in your .htaccess file?
-
When SSL enabled double check that you clear AbanteCart cache. What is your AbanteCart version?
-
already did. still same. is this server is configure wrongly?
btw im using v1.2.15. attach is my admin login page with error alert for reference
-
Admin warning is suppose to be there if you access admin via non-secure url and SSL enabled in AbanteCart settings
-
I think this is something related to SecurityMod, you need to contact your hosting company.
-
It is not security mod, browsers may block insecure request on secure page
https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content
-
Admin warning is suppose to be there if you access admin via non-secure url and SSL enabled in AbanteCart settings
i already setup the ssl and make changes using my local then push it to publish..but still the same.. :'( is this serve configuration or my php configuration wrong somewhere?
-
Hi.
This can be:
- issue in template
- invalid SSL ceritifcate
- htaccess misconfiguration
- store settings misconfiguration
- less possible but still, issue in 3rd party extension
- file cache or HTML cache or CDN if you have it