DB-4068 cherry-pick upstream HttpRequest/ObjectDecoder fixes (4.0.54/bdp 5.1)#22
Conversation
) Motivation: Technical speaking its valid to have http headers with no values so we should support it. That said we need to detect if these are "generated" because of an "invalid" fold. Modifications: - Detect if a colon is missing when parsing headers. - Add unit test Result: Fixes netty#9866 (cherry picked from commit a7c18d4) (After the default cherry-pick algorithm finished, I hand-resolved some compile errors related to refactoring between the 4.0 and 4.1 branches)
jtgrabowski
left a comment
There was a problem hiding this comment.
Backport looks good but I see some unchanged 4.0.54.Final in pom files
This version is equivalent to upstream's 4.0.54.Final, but with one upstream commit (for CVE-2019-20444) cherry-picked backwards from 4.1. Detect missing colon when parsing http headers with no value (netty#9871) GHSA-cqqj-4p63-rrmm netty#9866 netty#9871 a7c18d4
|
Thanks for creating an appropriate base branch. I found four overlooked
I updated the stale I've also deleted all Here's the diff reflecting what I just listed above, right before force-pushing: I'm force-pushing similar changes on the other two PRs. |
401e993 to
9d7e6fa
Compare
This build.yaml is copied from dse-netty-4.1.13.Final. I just modified the repo URL to point to https://repo.sjc.dsinternal.org/artifactory/datastax-releases-local instead of the old artifactory URL.
https://datastax.jira.com/browse/DB-4068
@dalaro I have netty write permissions so I created 4.0.54 branch and this PR