3 ms·
A lot of intelligent sounding words to explain a trivial bug: their network stack was using case-sensitive header names, which anyone doing anything remotely re
by brabel 5y ago
A lot of intelligent sounding words to explain a trivial bug: their network stack was using case-sensitive header names, which anyone doing anything remotely related to HTTP knows is a mistake.
We all make mistakes, but don't try to make it sound more grandiose ("a combination of multiple factors blah balh blah") than it is.
- viraptor 5y agoHttp2 and 3 are case sensitive at when encoding the headers: > As in HTTP/2, characters in field names MUST be converted to lowercase prior to their encoding. A request or response containing uppercase characters in field names MUST be treated as malformed https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-4.1.1-2 https://quicwg.org/base-drafts/draft-ietf-quic-http.html#sec...
- matsemann 5y ago> which anyone doing anything remotely related to HTTP knows is a mistake. Only if you haven't updated your knowledge since HTTP/1.1 days...