[HTTPS-Everywhere] Question not found on FAQ

[David A. Gershman]

> > Also, any chance of a "block non-https requests" feature so that if
> > 'https everywhere' can't make the switch for whatever reason, we can
> > just *not* make the request?
> 
> I agree that that would be useful.  Do you mean on a per-site basis or
> globally?  You can do it globally with a personal firewall rule and
> you can do it on a per-site basis with the Page Info trick above (by
> writing rules that point into file: or chrome: instead of http: for
> resources that turn out not to be available in https:).  Neither of
> these is very convenient, though.

Per-site would be nice, globally would be a handy quick fix. 
Unfortunately I can't use a personal firewall as at my work they use a
proxy server accessible only through http.  Even SSL requests require
the initial http proxy request: no port 80 allowed == no web access. :(

Thanks!

----------------------------------------
David A. Gershman
gershman at dagertech.net