Opened 10 years ago
Closed 10 years ago
#413 closed design (wontfix)
Requirement for handling bad chunking
Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
---|---|---|---|
Priority: | normal | Milestone: | unassigned |
Component: | p1-messaging | Severity: | In WG Last Call |
Keywords: | Cc: |
Description
3.3.1 Transfer-Coding -- "A server that receives a request message with a transfer-coding it does not understand SHOULD respond with 501..." There isn't a corresponding requirement for when 'chunked' is not the final coding, or occurs more than once. Should there be?
Change History (1)
comment:1 Changed 10 years ago by fielding@…
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
I don't think there needs to be. 400 is available in general. 501 is mentioned here because the message is valid.