http-parser
http-parser copied to clipboard
nodejs
http request/response parser for c
Hello, Do you know about [Conan](https://github.com/conan-io/conan)? [Conan](http://docs.conan.io/en/latest/) is modern dependency manager for C++. And will be great if your library will be available via package manager for other developers. [Here](https://github.com/bincrafters/conan-templates)...
See: https://github.com/nodejs/http-parser/pull/235#issuecomment-356903686 The `CONNECT_WITH_BODY_REQUEST` test case input has `Content-Length: 10` and a body `"blarfcicle"`, but the test expects [`.body= ""`](https://github.com/nodejs/http-parser/blob/master/test.c#L1102) ! [The RFC says](https://tools.ietf.org/html/rfc7230#section-3.3): > _The presence of a message...
`test.c` is over four thousand lines long and is getting a little hard to parse... any objections to moving some related tests into separate files in a `test/` directory? @indutny...
Right now the test suite has a proprietary/unique way of outputting the status of tests. It would be better if it used something like TAP, which is already used by...
According to https://www.w3.org/Protocols/HTTP/AsImplemented.html, HTTP/0.9 does not have header fields, and single CR + LF pair (or just LF) after a request line signals the end of request. But current http-parser...
If you try to install on OS X, you'll get this error ``` cc -I. -DHTTP_PARSER_STRICT=0 -Wall -Wextra -Werror -O3 -fPIC -c http_parser.c -o libhttp_parser.o cc -shared -o libhttp_parser.2.7.1.dylib libhttp_parser.o...
many post packet in same file, parsertrace.c did error!
many post header+body , is wrong! like qq outline.
Consider this code (from http_parser.c): ``` /* Transfer-Encoding: chunked */ case h_matching_transfer_encoding_chunked: parser->index++; if (parser->index > sizeof(CHUNKED)-1 || c != CHUNKED[parser->index]) { h_state = h_general; } else if (parser->index ==...
Given the header: ``` Transfer-Encoding: gzip, chunked\r\n ``` The parser will not set chunked encoding when it should: https://tools.ietf.org/html/rfc7230#section-3.3.1 Encodings are applied left to right and removed from right to...