3 ms·

At least HTTP/1.x is the default for command line testing and debugging. I'm a bit worried we'll lose testability of servers as we add more and more layers on t

by mojuba 5y ago

At least HTTP/1.x is the default for command line testing and debugging. I'm a bit worried we'll lose testability of servers as we add more and more layers on top of 1.x. Say it works with `curl` for me, what are the guarantees it will work the same way over HTTP/2 and /3 multiplexers?

jrockway 5y ago
curl already supports HTTP/2 and HTTP/3. It's true that you miss out on "telnet example.com 80" and typing "GET /", but that honestly hasn't been valid since HTTP/1.1 replaced HTTP/1.0. To some extent this all sounds to me like "I hate screws, they render my trusty hammer obsolete". That's true, but there are also great screw driving tools.
- NoGravitas 5y ago
  You could still do valid HTTP/1.1 over nc or telnet, or 'openssl s_client' if you needed TLS; it was just a matter of you knowing the protocol, and the minimum required headers for your use-case. (That said, curl is generally a better choice.)
  - Dylan16807 5y ago
    > or 'openssl s_client' if you needed TLS Which sites tend to need. I'm sure someone can make an equivalent to that. Maybe even just a wrapper around curl...
- otabdeveloper4 5y ago
  The only difference between HTTP/1.0 and HTTP/1.1 is having to send the 'Host:' header.