Skip to content
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

HTTPS for third-party domains #5

Open
jgmoss opened this issue May 17, 2016 · 3 comments
Open

HTTPS for third-party domains #5

jgmoss opened this issue May 17, 2016 · 3 comments

Comments

@jgmoss
Copy link

jgmoss commented May 17, 2016

Does this add-on convert third-party domains to HTTPS as well? For instance, if I visit a site and calls are made to another domain, are those requests also HTTPS?

@Rob--W
Copy link
Owner

Rob--W commented May 17, 2016

At the moment, the add-on only changes the default in the location bar. Nothing else is modified, but I've previously expressed interest in forcing everything to be https unless stated otherwise (that might break some websites though, so I haven't implemented it yet).

The good news is that http in https sites can be blocked. Active content such as scripts are blocked by default, images are enabled by default but you can also block them.

Go to about:config, search for mixed_content, and make sure that the following are set to true:

security.mixed_content.block_active_content
security.mixed_content.block_display_content

In Chrome, mixed content is

@EC-O-DE
Copy link

EC-O-DE commented Nov 7, 2017

+1 for an ext that redirects to HTTPS if available - and to HTTP if not availabe - of any url.

@fmarier
Copy link
Contributor

fmarier commented Nov 24, 2017

+1 for an ext that redirects to HTTPS if available - and to HTTP if not availabe - of any url.

Smart HTTPS (revived) might be what you are looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants