Why does HTTPS Everywhere need this permission all of a sudden? It worked fine without it before

Just write some script.
Jesus, I could do it in this post if I cared enough.

>needing an extension when Upgrade-Insecure-Requests: 1 would work in most cases

HTTPS is placebo anyway.

>Upgrade-Insecure-Requests: 1

Attached: сhrome.png (345x316, 35K)

> does what it is supposed to
> placebo

If you don’t know what you’re talking about then kindly fuck off.

Attached: image.jpg (645x729, 145K)

>all parts of a website load everything from the URL in address bar
Government schooling. so sad.

that's wrong tho
https everywhere rewrite links to cdn content if it's served in https too
you cannot easily modify tags without an extension

hasnt everyone moved on to smart https?

You wish.

>people unironically still use https everywhere

Attached: smarthttps.png (2149x1830, 400K)

lol enjoy your retarded extension
the way it works is stupid af, https everywhere is a more efficient approach

does smarthttps rewrite 3rd party http requests yet? that, apart from retarded web designers is the main reason for all of this.

but smart https is more efficent on RAM

You mean mixed content? If so, then yes. All the options are shown in that pic.

>waiting 6 seconds if a site is http only
yes, people are not so unironically retarded

>doesn't know ff 52esr also has this by default

>6 secs
And that's the first time you visit a site. After the first time it puts it in a whitelist if it isnt https and never takes longer again. Some sites are slow so this is actually wise. But it has never taken that long for me. You sound ignorant.

Smart HTTPS asks for the same permission.

>And that's the first time you visit a site.
I don't only use 9gag and facebook kiddo
>After the first time it puts it in a whitelist
just use https everywhere that has that included fucking retard
ignorance !== not wanting to do useless work someone else is already doing for me
smart https is a shitty extension and you should feel bad for promoting it, also it gives your browser an easily detectable fingerprint with this stupid request pattern

You are so wrong. Https everywhere uses a predefined list. So if its not on their list you're shit out of luck. It also lacks a lot of useful options. You have no idea what you're talking about.

So? I'm not updating before I find this shit out. Why didn't they use optional permissions?

I don't get it. I'm on 2018.6.21 and it's asking the permission for a new version. But looking at the changelog
github.com/EFForg/https-everywhere/commit/0d51161c0864a53d0762c4d15e02847ff1bb8b09#diff-a951caac7ef604fdff31e05ef8ca45d4
the permissions haven't even changed?
Is it a firefox bug?

I was literally just about to make this thread.

I upgraded to Smart Https. Hope it helps.

in the issue post
>prior history shows that it was before, which would require that permission) and for whatever reason firefox saw the new rule and asked for it yet again.
I only saw a "chromium" folder but I guess there's a different build for firefox.

So the permission has been there, it's just wanting it again.
github.com/EFForg/https-everywhere/issues/16377

why do i need this again?

Idk, why do you? I know why I use smart https.

>sites are configured wrong
>type "https"
That won't save you when the site accesses something over http that you can't "type https" to fix.

>what is mixed content

Install redirector
redirect:*
to:$1

smart https

>github.com/EFForg/https-everywhere/issues/16377
You know why goyim

Attached: botnet.png (695x391, 19K)

Thanks friendo.