http-parser
http-parser copied to clipboard
http request/response parser for c
Hi, I've fixed 4 dependencies missing and 1 dependency excessive reported. Those issues can cause incorrect results when http-parser is incrementally built. For example, any changes in "http-parser.h" will not...
implement support (with tests) for the following: - File URLS (no host part) `file:///tmp/some_file.txt` - magnet URLS (scheme:?query) `magnet:?t=urn:btih:c12fe1c06bba254a9dc9f519b335aa7c1367a88a&dn ` - Opaque URLS: `mailto:[email protected]`
When parsing URLs, treat an empty port (eg `http://hostname:/`) as if it were unspecified. RFC 3986 says: > URI producers and normalizers **SHOULD** omit the port component and its ":"...
Earlier http_parser_parse_url would incorrectly parse very long URLs: The resulting off and len parameters would just get truncated. Even though very long URLs are typically considered invalid by servers they...
Currently the on_headers_complete callback can return 0 to proceed with the response body, 1 to skip the body, and 2 to skip the body and stop looking for further messages,...
test.c line 4043, I add an assertion after the malloc function to fix the issue 465.
https://tools.ietf.org/html/rfc7230#section-3.3.3: ... any response with a 1xx (Informational), 204 (No Content), or 304 (Not Modified) status code is always terminated by the first empty line after the header fields, regardless...
Counting headers, URL and start lines separately because it was counting everything as headers before the headers_done state, throwing HPE_HEADER_OVERFLOW errors even when what really caused the overflow was the...
Spin out from https://github.com/nodejs/node/pull/24716. This also sets the default to 8KB when compiled via gyp.