- From: Willy Tarreau <w@1wt.eu>
- Date: Fri, 4 Sep 2020 10:21:36 +0200
- To: Stefan Eissing <stefan.eissing@greenbytes.de>
- Cc: Eric J Bowman <mellowmutt@zoho.com>, Ietf Http Wg <ietf-http-wg@w3.org>
On Fri, Sep 04, 2020 at 09:17:32AM +0200, Stefan Eissing wrote: > Many existing OCSP clients in servers (*cough*), use HTTP/1.0 to staple > certificates. Ah I didn't know, that's interesting! Now that you're speaking of this, I'm pretty sure we have somewhere and old HTTP client made to retrieve config files that's also 1.0 only. Often clients that speak 1.0 are those which want to advertise that they will *not* parse chunks and will instead consume data after the empty header till the end of the connection. > I have no data from the IoT devices of the world, but I would > suspect many of them will do as well. In the IoT world it tends to be awful, with code trying to imitate HTTP/1.1 using strstr() and consorts to find the relevant minimal parts :-/ Quite frankly it would be cleaner to stick to 1.0 sometimes! > Be happy when you can get away without supporting HTTP/0.9. ;) We disabled it by default 5 years ago in haproxy and didn't get any single complaint (except from the usual developer complaining that "GET /" on telnet now returns 400). So far so good :-) Willy
Received on Friday, 4 September 2020 08:21:55 UTC