-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warn about mixed content issues when changing the gateway #648
Labels
kind/enhancement
A net-new feature or improvement to an existing feature
Comments
lidel
added
kind/enhancement
A net-new feature or improvement to an existing feature
UX
labels
Jan 2, 2019
lidel
added a commit
that referenced
this issue
Jan 2, 2019
ghost
assigned lidel
Jan 2, 2019
lidel
added a commit
that referenced
this issue
Jan 7, 2019
* feat: warn about mixed content issues Closes #648
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: