Ticket #102 (closed design: wontfix)
Understanding Content-* on non-PUT requests
|Reported by:||email@example.com||Owned by:||firstname.lastname@example.org|
|Component:||p2-semantics||Severity:||Active WG Document|
RFC2616 Section 9.6 (PUT) places the following requirement on PUT recipients:
The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) headers that it does not understand or implement and MUST return a 501 (Not Implemented) response in such cases.
Does this advice apply to other request methods than PUT? E.g., POST? Should it apply to all requests with bodies?
- Priority set to normal
- Severity set to Active WG Document
- Milestone changed from unassigned to 11