Immediately after switching the page, it will work with CSR.
Please reload your browser to see how it works.

Source:https://github.com/SoraKumo001/next-streaming

⬅️ Censors Ignore Unencrypted HTTP/2 Traffic (2024)

puttycat 6 daysReload

Nice research, but I can only guess that this was fixed ten minutes after the report was published?

Naru41 6 daysReload

I don't see the point - ASCII vs. binary doesn't make any real difference. And there's no an actual unencrypted HTTP/2 traffic, so there's no incentive to censor.

userbinator 6 daysReload

The obvious follow-up is to then put a (possibly obfuscated) TLS connection in the request and response bodies, creating another tunneling method.

joshstrange 5 daysReload

Ok, I’ll ask the stupid question:

Why not use _Encrypted_ HTTP/2 traffic? The article goes on and on about HTTP 1.1 and unencrypted HTTP 2.0 but never once mentioned encrypted HTTP 2.0 which I would assume shares the exact same binary/“hard to block” characteristics of unencrypted HTTP 2.0.

I can only assume that everyone knows why that’s already blocked in China, but I don’t

graemep 5 daysReload

Maybe they monitor rather than censor unencrypted traffic? That could be more of a problem for those in authoritarian countries.