Closed Bug 1455614 Opened 7 years ago Closed 1 year ago

Comma-separated Content-Length with unequal values should be rejected

Categories

(Core :: Networking: HTTP, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
115 Branch
Tracking Status
firefox115 --- fixed

People

(Reporter: annevk, Assigned: smayya)

References

Details

(Whiteboard: [necko-triaged][necko-priority-queue], [wptsync upstream])

Attachments

(1 file)

See tests at https://github.com/w3c/web-platform-tests/pull/10548. I think at the very least we should start rejecting values such as Content-Length: 42,30 while continuing to support Content-Length: 42,42 As long as we don't, we would parse the above differently from Content-Length: 42 Content-Length: 30 which seems suboptimal.
Priority: -- → P3
Whiteboard: [necko-triaged]
Severity: normal → S3

The Content-Length parsing is here

WPT here

Priority: P3 → P2
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-queue]
Assignee: nobody → smayya
Attachment #9334683 - Attachment description: WIP: Bug 1455614- improve content-length header parsing → Bug 1455614- improve content-length header parsing. r=#necko
Attachment #9334683 - Attachment description: Bug 1455614- improve content-length header parsing. r=#necko → Bug 1455614 - improve content-length header parsing. r=#necko
Pushed by smayya@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9865f9ad00a4 improve content-length header parsing. r=necko-reviewers,valentin
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/40282 for changes under testing/web-platform/tests
Whiteboard: [necko-triaged][necko-priority-queue] → [necko-triaged][necko-priority-queue], [wptsync upstream]
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: