* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #180 (closed editorial: fixed)

Opened 5 years ago

Last modified 2 years ago

Note special status of Content-* prefix in header field registration procedures

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 11
Component: non-specific Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/65457B9D-A1E1-4A55-B5C9-AF19A323B87F@mnot.net

Description

As per #103, header fields whose name starts with 'content-' have special meaning, placing additional requirements upon implementations. This needs to be noted in the registration procedures, for the information of IANA, the IESG and any expert reviewer.

Note that the resolution of #104 may obviate this.

Change History

comment:1 Changed 4 years ago by julian.reschke@gmx.de

  • Priority set to normal
  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from unassigned to 11

moved into #231

comment:2 Changed 4 years ago by fielding@gbiv.com

From [1158]:

Replaced the general prohibition on unrecognized Content-* header fields with a specific prohibition of Content-Range (the only field for which it is an actual problem) and a general requirement regarding checking for consistency. Unfortunately, this required rewriting the entire section on PUT to get rid of the misconceptions about storing resources and reflect how PUT is actually implemented in practice.

Addresses #79, #102, #103, #104, #112, #180, #231, and #267

comment:3 Changed 2 years ago by julian.reschke@gmx.de

  • Summary changed from Note special status of Content-* prefix in header registration procedures to Note special status of Content-* prefix in header field registration procedures
Note: See TracTickets for help on using tickets.