Skip to content

fix(http): HttpHeaderParser improperly handled quoted parameter values#5897

Merged
bluestreak01 merged 4 commits intomasterfrom
raph_http_boundary
Jul 10, 2025
Merged

fix(http): HttpHeaderParser improperly handled quoted parameter values#5897
bluestreak01 merged 4 commits intomasterfrom
raph_http_boundary

Conversation

@RaphDal
Copy link
Copy Markdown
Contributor

@RaphDal RaphDal commented Jul 7, 2025

This PR fixes #5757 by reworking the HttpParserHeader to be more compliant with the HTTP RFC when parsing Content-Type.

When HttpParserHeader was parsing the boundary parameter it would just read every chars until the ; delimiter, ignoring if the value was quoted.

Users may now use any compliant HTTP clients and the server should be able to parse their requests and answer correctly to them.

@bluestreak01 bluestreak01 merged commit 4beeb6a into master Jul 10, 2025
8 of 30 checks passed
@bluestreak01 bluestreak01 deleted the raph_http_boundary branch July 10, 2025 09:54
@glasstiger
Copy link
Copy Markdown
Contributor

[PR Coverage check]

😍 pass : 77 / 85 (90.59%)

file detail

path covered line new line coverage
🔵 io/questdb/cutlass/http/HttpSemantics.java 12 14 85.71%
🔵 io/questdb/cutlass/http/HttpHeaderParser.java 52 58 89.66%
🔵 io/questdb/std/str/Utf8s.java 7 7 100.00%
🔵 io/questdb/cutlass/http/HttpHeaderParameterValue.java 6 6 100.00%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The /imp rest endpoint does not support quoted multipart boundary definition

3 participants