3 ms·
The HTTP specification does tell you to behave differently depending on the presence or absence of specific values for case-insensitive headers. That requires d
by lmm 5y ago
The HTTP specification does tell you to behave differently depending on the presence or absence of specific values for case-insensitive headers. That requires decoding the header name strings.
- coldtea 5y ago>That requires decoding the header name strings. Which should be ascii though no?
- lmm 5y agoMaybe, but it's not "treating strings as opaque encoded bytes" which is what was asked.
- lhorie 5y agoASCII is kinda special in that it's both a way of encoding strings and it has character-to-byte equivalence. You can specify an HTTP header as being any number of characters between `\n\r` characters or any number of bytes between `0x0A 0x0D`, and the parsing code is going to compile to pretty much the same thing regardless of whether you know what `0x0A` means or not.
- lmm 5y agoRight, but to do case-insensitive comparisons of header names you need to decode them as strings, not just byte sequences.