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

Fwd: Rev05 nits

From: Jim Gettys <jg@pa.dec.com>
Date: Tue, 3 Nov 1998 10:07:56 -0800
Message-Id: <9811031807.AA25337@pachyderm.pa.dec.com>
To: http-wg@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/137
Dave sent me some nits off line; as we are in the final throes, I want
it in the record.
				- Jim

attached mail follows:

You just *knew* you would hear from me, didn't you!? :-)
Some nits for the next go-round.


Have you noticed there's no Page 2 in the PostScript versions?!
Another gift from Word.

5.1.2 Request-URI

   The Request-URI is a Uniform Resource Identifier (section 3.2) and
   identifies the resource upon which to apply the request.

          Request-URI    = "*" | absoluteURI | abs_path | authority

   The three options for Request-URI are dependent on the nature of the

There are evidently four now.

14.16 Content Range
   When an HTTP message includes the content of multiple ranges (for
   example, a response to a request for multiple non-overlapping
   ranges), these are transmitted as a multipart message. The multipart
   media type used for this purpose is "multipart/byteranges" as defined
   in appendix 19.2. See appendix 19.6.3for a compatibility issue.
   					^-- insert space

19.6.3 Changes from RFC 2068
   worth fixing [39]. TE also solves another, obscure, downward
   interoperability problem that could have occured due to interactions
   					    ======= -> occurred
   between authentication trailers, chunked encoding and HTTP/1.0
   clients.(Section 3.6, 3.6.1, and 14.39)
Received on Tuesday, 3 November 1998 10:12:03 UTC

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