Fwd: Rev05 nits
Jim Gettys (jg@pa.dec.com)
Tue, 3 Nov 1998 10:07:56 -0800
This is a multi-part message in MIME format, created by Pachyderm.
The parts are separated by "--1" lines.
The first part is a covering note, the others are attachments.
--1
Content-Type: text/plain
Dave sent me some nits off line; as we are in the final throes, I want
it in the record.
- Jim
--1
Content-Type: message/rfc822
Content-Disposition: inline
Received: by src-mail.pa.dec.com; id AA22189; Thu, 17 Sep 1998 12:53:17 -0700
Received: from mail1.digital.com by pobox1.pa.dec.com (5.65v3.2/1.1.10.5/07Nov97-1157AM)
id AA20009; Thu, 17 Sep 1998 12:50:49 -0700
Received: from www10.w3.org (www10.w3.org [18.23.0.20])
by mail1.digital.com (8.8.8/8.8.8/WV1.0g) with ESMTP id MAA01513
for <jg@pa.dec.com>; Thu, 17 Sep 1998 12:49:37 -0700 (PDT)
Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by www10.w3.org (8.8.5/8.7.3) with SMTP id PAA14758 for <jg@w3.org>; Thu, 17 Sep 1998 15:46:03 -0400 (EDT)
Received: from research.research.bell-labs.com ([135.104.1.3]) by dirty; Thu Sep 17 15:44:39 EDT 1998
Received: from starling.research.bell-labs.com ([135.104.26.187]) by research; Thu Sep 17 15:44:38 EDT 1998
Received: from aleatory.research.bell-labs.com (aleatory.research.bell-labs.com [135.104.46.50])
by starling.research.bell-labs.com (8.9.1/8.9.1) with ESMTP id PAA23250;
Thu, 17 Sep 1998 15:44:36 -0400 (EDT)
Received: (from dmk@localhost)
by aleatory.research.bell-labs.com (8.8.6/8.8.6) id PAA16406;
Thu, 17 Sep 1998 15:44:35 -0400 (EDT)
Date: Thu, 17 Sep 1998 15:44:35 -0400 (EDT)
From: Dave Kristol <dmk@research.bell-labs.com>
Message-Id: <199809171944.PAA16406@aleatory.research.bell-labs.com>
To: jg@w3.org
Subject: Rev05 nits
Status:
MIME-Version: 1.0
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.
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)
--1--