Re: proposed change for Issue 103 (content-*)

Dan Winship wrote:
> Julian Reschke wrote:
>> OLD:
>>
>>   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.
>>
>> NEW:
>>
>>   NOT ignore any Content-* headers (e.g. headers starting with the
>>   prefix 'Content-') that it does not understand or implement and MUST
>>   return a 501 (Not Implemented) response in such cases.
> 
> s/e.g./i.e./. (Or just get rid of it.) Otherwise it suggests that there
> are "Content-* headers" that don't start with "Content-".

Good catch. So

OLD:

    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.

NEW:

    NOT ignore any Content-* headers (headers starting with the prefix
    'Content-') that it does not understand or implement and MUST return
    a 501 (Not Implemented) response in such cases.

BR, Julian