| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| cherry-pick.v2.9.4-4-g805a0d1.fix-test-numbers.patch | Fix test numbers PR-URL: https://github.com/nodejs/http-parser/pull/511 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> |
no | v2.9.4-4-g805a0d1 <https://github.com/joyent/http-parser/commit/805a0d1> | 2020-05-04 | ||
| cherry-pick.v2.9.4-6-gd9275da.fix-wsign-compare-warning.patch | Fix -Wsign-compare warning The operands to `+` are promoted from `uint16_t` to `int` before addition, making the expression `off + len <= buflen` emit a warning because `buflen` is unsigned. Fixes: https://github.com/nodejs/http-parser/issues/514 PR-URL: https://github.com/nodejs/http-parser/pull/515 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> |
no | v2.9.4-6-gd9275da <https://github.com/joyent/http-parser/commit/d9275da> | 2020-05-15 | ||
| cherry-pick.v2.9.4-7-g4b99e42.test-content-length-header-parsing.patch | Test Content-Length header parsing The test suite did very little validation of the Content-Length field until now. Verify for each request and response that the parsed numeric value matches the value from the header field. PR-URL: https://github.com/nodejs/http-parser/pull/519 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> |
no | v2.9.4-7-g4b99e42 <https://github.com/joyent/http-parser/commit/4b99e42> | 2020-07-08 | ||
| cherry-pick.v2.9.4-8-ge13b274.allow-content-length-and-transfer-encoding-chunked.patch | Allow Content-Length and Transfer-Encoding: chunked Fixes: https://github.com/nodejs/http-parser/issues/517 PR-URL: https://github.com/nodejs/http-parser/pull/518 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Pierce Lopez <pierce.lopez@gmail.com> |
no | v2.9.4-8-ge13b274 <https://github.com/joyent/http-parser/commit/e13b274> | 2020-07-10 | ||
| cherry-pick.v2.9.4-9-g4f15b7d.fix-sizeof-http-parser-assert.patch | Fix sizeof(http_parser) assert The result should be 32 on both 32 bits and 64 bits x86 because of struct padding. Fixes: https://github.com/nodejs/http-parser/issues/507 PR-URL: https://github.com/nodejs/http-parser/pull/510 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> |
yes | upstream | v2.9.4-9-g4f15b7d <https://github.com/joyent/http-parser/commit/4f15b7d> | 2020-07-10 | |
| CVE-2020-8287.patch | [PATCH] http: unset `F_CHUNKED` on new `Transfer-Encoding` Duplicate `Transfer-Encoding` header should be a treated as a single, but with original header values concatenated with a comma separator. In the light of this, even if the past `Transfer-Encoding` ended with `chunked`, we should be not let the `F_CHUNKED` to leak into the next header, because mere presence of another header indicates that `chunked` is not the last transfer-encoding token. |
Fedor Indutny <fedor@indutny.com> | no | Upstream PR (from nodejs) https://github.com/nodejs/http-parser/pull/530 | 2022-08-05 | |
| debian.improve-installation.patch | Improve installation * Make LIBDIR overridable from debian/rules * Install the .a file |
Christoph Biedl <debian.axhn@manchmal.in-ulm.de> | not-needed | 2020-02-24 |