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

Re: Rev05 nits

From: Jim Gettys <jg@pa.dec.com>
Date: Wed, 11 Nov 1998 11:10:04 -0800
Message-Id: <9811111910.AA28931@pachyderm.pa.dec.com>
To: Dave Kristol <dmk@research.bell-labs.com>
Cc: http-wg@hplb.hpl.hp.com

> From: Dave Kristol <dmk@research.bell-labs.com>
> Date: Thu, 17 Sep 1998 15:44:35 -0400 (EDT)
> To: jg@w3.org
> Subject: Rev05 nits
> -----
> You just *knew* you would hear from me, didn't you!? :-)
> Some nits for the next go-round.
> 
> Dave
> -------------
> 
> 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.\

So I can't count...

> 
> 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

Yup.

> 
> 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)

So Word can't spell, either...  I guess I should do a final spelling
check...
			- Jim
Received on Wednesday, 11 November 1998 19:10:15 EST

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