W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Text of changes proposed at bof (7.14.3,13.5,16.11,18.18,18.30)

From: Ted Hardie <hardie@merlot.arc.nasa.gov>
Date: Tue, 21 May 1996 11:05:36 -0700 (PDT)
Message-Id: <199605211805.LAA20294@merlot.arc.nasa.gov>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Here is the text for the changes I suggested at the HTTP Bof in Paris:

For 7.14.3 Content Ranges

Delete:

      If the last-byte-pos value is present, it must be greater than or equal
      to the first-byte-pos in that byte-range-spec, or the byte-range-spec is
      invalid.  The recipient of an invalid byte-range-spec must ignore it.
  and
      If the last-byte-pos value is larger than the current length of the
      entity, it is assumed to be equal to the current length of the entity.	 

Insert after "If the last-byte-pos value is absent":

      If the last-byte-pos value is present, it must represent a possible
      value within the byte-range-spec.  It must be greater than or equal
      to the first-byte-pos in the byte-range-spec and less than or equal
      to the current length of the entity in bytes.  Similarly, if the first-
      byte-pos is present, it must represent a possible value.  It must be 
      greater than or equal to zero and it must not be greater than the 
      last-byte-pos value.  The recipient of an invalid byte-range-spec
      must ignore it and return the entire entity.


For 13.5 PUT

Replace:

      If the request passes through a cache and the Request-URI identifies a
      currently cached entity, that entity MUST be removed from the cache.

with:

      If the request passes through a cache and the Request-URI identifies a
      currently cached entity, the entity MUST be marked stale unless
      the cache receives a response with a status code in the 400 range.

For 16.11 Write-Through Mandatory
				
Replace:

	A cache MUST NOT reply to such a request from a client before having
	transmitted the request to the inbound server, and having received
	a corresponding response from the inbound server.

With:

	A cache MAY send a 100 Continue response to such a request, but a
	a cache MUST NOT otherwise reply to such a request before having
	transmitted the request to the inbound server and having received
	a corresponding response from the inbound server.


For 18.18 Content-Range

There are several references to HTTP/1.0 which should be to HTTP/1.1.

For 18.30

The text several times uses the term "sender".  My first reading of
this was that "sender" meant "origin server"; if so, it would be
clearer to say "origin server" throughout.  If "sender" means "origin
server, cache, or proxy", then that should be spelled out at least
once.  
Received on Tuesday, 21 May 1996 11:07:34 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:00 EDT