issue 79: must understand content-* header fields or fail

The editors spent some time discussing

   http://trac.tools.ietf.org/wg/httpbis/trac/ticket/79

with regard to the requirement in RFC 2616, section.9.6,
the description of PUT:

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

The purpose of this requirement was to enable some future
use of Content-Range for the purpose of partial updates.

No server that I am aware of supports that requirement.
Partial updates should be accomplished using a new method
(PATCH) rather than a retroactive requirement on deployed
services that nobody implemented.

My proposal is to remove that sentence from the spec and
note in the changes section that the requirement was removed
in favor of deploying PATCH.

....Roy

Received on Thursday, 30 July 2009 10:24:39 UTC