Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#180 closed editorial (fixed)

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

Reported by: mnot@… Owned by:
Priority: normal Milestone: 11
Component: non-specific Severity: Active WG Document
Keywords: Cc:

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 (3)

comment:1 Changed 9 years ago by julian.reschke@…

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

moved into #231

comment:2 Changed 8 years ago by fielding@…

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 7 years ago by julian.reschke@…

  • 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.