#103 closed design (fixed)
Content-*
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | Milestone: | unassigned | |
Component: | p2-semantics | Severity: | |
Keywords: | Cc: |
Description
What does Content-* mean? Does it mean all headers prefixed with "Content-", or just those headers prefixed by "Content-" that are defined in RFC 2616?
Attachments (2)
Change History (6)
comment:1 Changed 15 years ago by fielding@…
comment:2 Changed 14 years ago by julian.reschke@…
- Owner set to julian.reschke@…
- Status changed from new to assigned
comment:3 Changed 14 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from assigned to closed
comment:4 Changed 12 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.
Note: See
TracTickets for help on using
tickets.
It means all header fields that strat with the prefix "Content-", regardless of where they were defined.