Slight editorial discrepancy in HTTP/1.1 Rev 3

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Dave Kristol: "Re: TE: identity; q=0"
• Previous message: Arthur P. Goldberg: "Comments on draft HTTP/1.1 spec, v3"
• Next in thread: Jeffrey Mogul: "Re: Slight editorial discrepancy in HTTP/1.1 Rev 3"
• Reply: Jeffrey Mogul: "Re: Slight editorial discrepancy in HTTP/1.1 Rev 3"

Hi,

While reviewing Rev 3 in conjunction with some testing I found this slight
discrepancy:

In Section 10.4.17 (416 Requested Range Not Satisfiable) it is stated:

"When this status code is returned for a byte-range request, the response
MUST include a Content-Range entity-header field specifying the current
length of the selected resource (see section 14.16)."

In section 14.16 (Content-Range) it is stated:

"A server sending a response with status code 416 (Requested range not
satisfiable) SHOULD include a Content-Range field with a
byte-range-resp-spec of "*""

The discrepancy is between the directives MUST and SHOULD.

Regards,

John Chamberlain
Iris Associates
mailto:john_chamberlain@iris.com

• Next message: Dave Kristol: "Re: TE: identity; q=0"
• Previous message: Arthur P. Goldberg: "Comments on draft HTTP/1.1 spec, v3"
• Next in thread: Jeffrey Mogul: "Re: Slight editorial discrepancy in HTTP/1.1 Rev 3"
• Reply: Jeffrey Mogul: "Re: Slight editorial discrepancy in HTTP/1.1 Rev 3"