Comment by josephg
3 years ago
What are the downsides of using http/1.1 or unencrypted http2 from a docker container?
I’m imagining an application server in a docker container talking to a load balancer, in the same data center. I can see some advantages to http2 (head of line blocking, header compression and multiplexing probably bring some performance benefits). But why do you want http3?
Most http/2 implementations enforce valid certificates, just like http/3.
gRPC requires http/2.
Some software like the aforementioned accursed GIS product refuse to work over unencrypted HTTP. They even ignore the load balancer headers like X-Forwarded-Proto just to be extra irritating.