Skip to content

Comment on HTTP/2 rapid reset attack impacting Nginx productsparent

Comments

you need to change a setting to even be able to access a HTTP url.

No. http://captive.apple.com seems to load just fine for me.

I will always use HTTP/1.1 on port 80 but my customers wont be able to connect even if they try, my only option is to tell them to uninstall their anti-virus and hope that works.

Because of infrastructure malware like ad injectors at ISPs, it's probably in your customers best interests to use HTTPS.

Hell, it's better to use HTTPS with a self signed cert than HTTP.

hurts a producer that is not complying with the authority.

There's always the risk of a conspiracy of vendors deplatforming someone. That's true. I'd be more worried about your ISPs or electricity companies unilaterally shutting off your service.

If you see Letsencrypt going all political, like Patreon, and kicking off people with the wrong views, then yeah we have a problem.

They will say that to use unencrypted protocols you need a license from your government.

Haha, the wind is blowing the other way, buddy.

It loads fine because you enabled it.

Default chrome. I'm not even aware of the option you mention.

Yup. Tried on desktop and android chrome.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.