[zinekeller]

Unfortunately, I'll indeed slide with FF and Chroke here, because we attempted a plaintext h2 (that was 2015, where HTTPS awareness are becoming mainstream) and unless you bothered to put it into another port it just unpredictably stops due to proxies mangling it.

In an internal study (in an enterprise level) and assuming this is HTTP/1.1, that some proxies will either cache only brotli and made it inaccesible to gzip-only clients (even when you bothered with Vary, because they're plain broken in that regard) or just barf with it and time-out not only that particular request but crash a proxy.

The problem for large-scale deployment is that there are transparent proxies in Timbuktu (literally) since data is not cheap there, they need to use HTTP proxies to compress that, not to mention dial-up users in the US! (Good luck, Verizon!)