4 ms·
I really don’t understand what you mean by this. I’ve never thought http was difficult. What is it that you find problematic?
by je_bailey 6y ago
I really don’t understand what you mean by this. I’ve never thought http was difficult. What is it that you find problematic?
- nly 6y agoLegacy HTTP/1.1 suffers a few issues, see the current RFC errata: https://www.rfc-editor.org/errata_search.php?rfc=7230&rec_status=15&presentation=records https://www.rfc-editor.org/errata_search.php?rfc=7230&rec_st... There are issues particularly around how whitespace and obsolete line folding should be handled Various whitespace issues in node.js: https://github.com/nodejs/http-parser/issues?q=is%3Aissue+whitespace https://github.com/nodejs/http-parser/issues?q=is%3Aissue+wh... Spec clarification: https://github.com/httpwg/http-core/issues/53 https://github.com/httpwg/http-core/issues/53 Node.js's parser was at one point replacing all white space in headers with a single space character, even though until recently this was non-conformant (you were only supposed to do so with obs-fold). It did this so it didn't have to buffer characters (since http-parser is a streaming parser). It's not as trivial as a few string splits. Node.js's parser is ~2,500 lines of C code.