W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 1998

Slight editorial discrepancy in HTTP/1.1 Rev 3

From: <jchamberlain@iris.com>
Date: Wed, 29 Apr 1998 15:30:14 +0100 (BST)
To: http-wg@cuckoo.hpl.hp.com
Message-Id: <852565F5.004D5602.00@motorcity2.lotus.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/90


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

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.


John Chamberlain
Iris Associates
Received on Thursday, 30 April 1998 05:31:23 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:05 UTC