Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>That requires decoding the header name strings.

Which should be ascii though no?



Maybe, but it's not "treating strings as opaque encoded bytes" which is what was asked.


ASCII 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.


Right, but to do case-insensitive comparisons of header names you need to decode them as strings, not just byte sequences.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: