You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The options UI should display a warning about content being blocked because of mixed-content protections when the “Custom Local Gateway” option doesn't match the pattern https://.*/|http://127\.\d+\.\d+\.\d+:\d+/ (any HTTPS origin, or any origin on the loopback interface). This only needs to be visible when the pattern doesn't match.
Configurations like #19/#328/#604 and #645 all indicate that such a warning would be useful.
My own blog loads over HTTPS with images being loaded over IPFS. Someone contacted me to complain that images weren't loading, and after some troubleshooting we found out he had his IPFS Companion extension pointed at another IP address on his local network; which resulted in the same type of mixed content issues as other users have reported.
The text was updated successfully, but these errors were encountered:
The options UI should display a warning about content being blocked because of mixed-content protections when the “Custom Local Gateway” option doesn't match the pattern
https://.*/|http://127\.\d+\.\d+\.\d+:\d+/
(any HTTPS origin, or any origin on the loopback interface). This only needs to be visible when the pattern doesn't match.Mockup: /ipfs/QmezHbfHAg7NyzrbqgeRpvJJPx5h7eikHb77HLBwkm5jps
Configurations like #19/#328/#604 and #645 all indicate that such a warning would be useful.
My own blog loads over HTTPS with images being loaded over IPFS. Someone contacted me to complain that images weren't loading, and after some troubleshooting we found out he had his IPFS Companion extension pointed at another IP address on his local network; which resulted in the same type of mixed content issues as other users have reported.
The text was updated successfully, but these errors were encountered: