This topic was already raised once in the past (see
https://lists.eff.org/pipermail/https-everywhere/2011-June/000914.html)
but I'd like to discuss it again because it's pretty annoying and might
even be disturbing to new users of the extension.
I found that the main problem are websites that
Chrome now warns about this too, per:
https://code.google.com/p/chromium/issues/detail?id=253249
Looks like it's on the beta channel (M37) which will probably hit stable in
~one month.
On Wed, Aug 20, 2014 at 1:10 PM, Richard Fussenegger, BSc <
[email protected]> wrote:
> This topic was
I wasn't able to reproduce this prompt on Tumblr, in a fresh FF31.0
profile with only HTTPS Everywhere installed. Is there another site
that reproduces reliably?
I would be mildly in favor of search the page after load for form
elements where action points to an insecure URL that we can rewrit
You can easily reproduce the problem on any page by simply altering a
forms action attribute to use the HTTP scheme with the developer console
(in Firefox and Chrome). I couldn't find a public available website with
the explained issue that also has a ruleset defined. I created the
following te
+1 for a stable promotion!
On Tue, Aug 19, 2014 at 4:21 PM, Dave Warren wrote:
> On 2014-08-19 13:46, Jacob S Hoffman-Andrews wrote:
>
>> We've had a Chrome version of HTTPS Everywhere for a while, and it seems
>> to work pretty well. What do you all think of promoting it from Beta to
>> Stable
