Context Navigation

← Previous Ticket
Next Ticket →

#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)

343.diff (1.2 KB) - added by julian.reschke@… 8 years ago.: Proposed patch
343.2.diff (1.5 KB) - added by julian.reschke@… 7 years ago.: Proposed patch removing the deprecation and describing potential issues.
343.3.diff (1.5 KB) - added by julian.reschke@… 7 years ago.: Proposed patch removing the deprecation and describing potential issues.

Download all attachments as: .zip

Change History (14)

Changed 8 years ago by julian.reschke@…

Attachment 343.diff added

Proposed patch

comment:1 Changed 8 years ago by mnot@…

Milestone changed from unassigned to 19

comment:2 Changed 8 years ago by julian.reschke@…

From [1535]:

Discourage use of chunk-extensions and deprecate definition of new ones (see #343)

comment:3 Changed 8 years ago by julian.reschke@…

Resolution set to incorporated
Status changed from new to closed

comment:4 Changed 8 years ago by mnot@…

Resolution incorporated deleted
Status changed from closed to reopened

comment:5 Changed 8 years ago by mnot@…

Resolution set to fixed
Status changed from reopened to closed

comment:6 Changed 7 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>)