Opened 10 years ago
Closed 10 years ago
#411 closed design (fixed)
Requirements for recipients of ws between start-line and first header field
Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
---|---|---|---|
Priority: | normal | Milestone: | 22 |
Component: | p1-messaging | Severity: | In WG Last Call |
Keywords: | Cc: |
Description
3.1 Request Line -- There isn't a requirement for recipients of messages with whitespace between the start-line and the first header field. Should there be?
Change History (5)
comment:1 Changed 10 years ago by fielding@…
comment:2 Changed 10 years ago by fielding@…
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 10 years ago by fielding@…
- Milestone changed from unassigned to 22
comment:4 Changed 10 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:5 Changed 10 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
From [2028]:
Expand on message parsing robustness regarding whitespace. Clarify that whitespace-delimited parsing by recipients is allowed.
Add requirement on recipients of whitespace between start-line and first header field to be consistent with implementations and safe from the header spoofing issues.
Reduce ABNF conformance by recipients to a SHOULD.
Addresses #411, #412, and #414.