Opened 10 years ago

Closed 10 years ago

#457 closed editorial (incorporated)

Registering x-gzip and x-deflate

Reported by: mnot@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 23
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:


p1 section 7.5 defines the transfer (and content) coding registry.

Earlier in the spec, we talk about x-gzip and x-deflate being synonyms for gzip and deflate, respectively.

Should we register them as well, then? Note that RFC6648 allows registration of X- parameters.

(they should probably be explicitly deprecated)

Change History (2)

comment:1 Changed 10 years ago by fielding@…

From [2285]:

(editorial) Register x-gzip and x-compress; add a reference for compress; clean up the coding descriptions to be consistent with the referenced sources; addresses #457

comment:2 Changed 10 years ago by fielding@…

  • Milestone changed from unassigned to 23
  • Resolution set to incorporated
  • Status changed from new to closed

Note that this affects both p1 (transfer codings) and p2 (content codings).

Note: See TracTickets for help on using tickets.