Opened 11 years ago
Closed 9 years ago
#343 closed design (fixed)
chunk-extensions
Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
---|---|---|---|
Priority: | normal | Milestone: | 24 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Right now, this is all we say about chunk-extensions (beyond the BNF, etc.):
All HTTP/1.1 applications MUST be able to receive and decode the "chunked" transfer-coding and MUST ignore chunk-ext extensions they do not understand.
Since this is an extensibility point, we should give guidance on how it should be used.
I can't really see establishing a chunk-extension registry; they don't have any semantic, and AFAIK haven't really been used in anger.
Proposal - add
""" Use of chunk-extensions by senders is deprecated; they SHOULD NOT be sent and definition of new chunk-extensions is discouraged. """
Attachments (3)
Change History (14)
Changed 11 years ago by julian.reschke@…
comment:1 Changed 11 years ago by mnot@…
- Milestone changed from unassigned to 19
comment:2 Changed 11 years ago by julian.reschke@…
comment:3 Changed 11 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from new to closed
comment:4 Changed 11 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:5 Changed 11 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
comment:6 Changed 9 years ago by julian.reschke@…
- Milestone changed from 19 to unassigned
- Resolution fixed deleted
- Status changed from closed to reopened
Reconsider the deprecation (see <http://lists.w3.org/Archives/Public/ietf-http-wg/2013JulSep/1190.html>), and maybe add a note that this is a connection-level feature (see <lists.w3.org/Archives/Public/ietf-http-wg/2013JulSep/1202.html>)
Changed 9 years ago by julian.reschke@…
Proposed patch removing the deprecation and describing potential issues.
Changed 9 years ago by julian.reschke@…
Proposed patch removing the deprecation and describing potential issues.
comment:7 Changed 9 years ago by julian.reschke@…
comment:8 Changed 9 years ago by julian.reschke@…
- Milestone changed from unassigned to 24
- Resolution set to incorporated
- Status changed from reopened to closed
comment:9 Changed 9 years ago by fielding@…
comment:10 Changed 9 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:11 Changed 9 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Proposed patch