- From: John Franks <john@math.nwu.edu>
- Date: Fri, 31 May 1996 13:32:59 -0500 (CDT)
- To: jg@w3.org
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Perhaps this is a little nit-picky, but there are a number of places
where "entity" is used when "entity-body" is meant. Usually this is
harmless, but with phrases like "the total size of the entity" or in
discussion of content-encoding it could cause confusion.
In the excerpts that follow, I believe that all occurences of
entity
^^^^^^
(marked with ^^^^^) should be replaced with entity-body.
John Franks
##########################
11 Access Authentication
...
If the server does not wish to accept the credentials sent with a
request, it SHOULD return a 401 (Unauthorized) response. The response
MUST include a WWW-Authenticate header field containing the (possibly
new) challenge applicable to the requested resource and an entity
^^^^^
explaining the refusal.
##########################
13.4.4 Combining Byte Ranges
A response may transfer only a subrange of the bytes of an entity,
^^^^^^
either because the request included one or more Range specifications, or
because a connection was broken prematurely. After several such
transfers, a cache may have received several ranges of the same entity.
^^^^^^
If a cache has a stored non-empty set of subranges for an entity, and an
^^^^^^
incoming response transfers another subrange, the cache MAY combine the
new subrange with the existing set if both the following conditions are
met:
##########################
13.5 Caching Negotiated Responses
Use of server-driven content negotiation (section 12), as indicated by
the presence of a Vary header field in a response, alters the conditions
and procedure by which a cache can use the response for subsequent
requests.
A server MUST use the Vary header field (section 14.43) to inform a
cache of what header field dimensions are used to select among multiple
representations of a response. These are called the "selecting" request-
headers. A cache can use the selected representation (the entity
^^^^^^
included with that particular response) for replying to subsequent
requests on that resource only when the subsequent requests have the
##########################
14.12 Content-Encoding
The Content-Encoding entity-header field is used as a modifier to the
media-type. When present, its value indicates what additional content
codings have been applied to the entity, and thus what decoding
^^^^^^
mechanisms MUST be applied in order to obtain the media-type referenced
by the Content-Type header field. Content-Encoding is primarily used to
allow a document to be compressed without losing the identity of its
underlying media type.
...
The Content-Encoding is a characteristic of the entity identified by the
Request-URI. Typically, the entity is stored with this encoding and is
^^^^^^
only decoded before rendering or analogous usage.
The Content-Encoding is a characteristic of the entity identified by the
Request-URI. Typically, the entity is stored with this encoding and is
^^^^^^
only decoded before rendering or analogous usage.
##########################
14.13 Content-Language
The Content-Language entity-header field describes the natural
language(s) of the intended audience for the enclosed entity. Note that
^^^^^^
this may not be equivalent to all the languages used within the entity.
##########################
The Content-Range header is sent with a partial entity-body to specify
where in the full entity-body the partial body should be inserted. It
also indicates the total size of the entity.
^^^^^^ (should be "full entity-body")
##########################
If the server ignores a byte-range-spec because it is invalid, the
server should treat the request as if the invalid Range header field did
not exist. (Normally, this means return a 200 response containing the
full entity). The reason is that the only time a client will make such
^^^^^^
an invalid request is when the entity is smaller than the entity
retrieved by a prior request.
Received on Friday, 31 May 1996 11:37:03 UTC