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

Re: Accept-Transfer header field (was HTTP/1.1 Issues: TRAILER_FIELDS)

From: Larry Masinter <masinter@parc.xerox.com>
Date: Wed, 19 Nov 1997 10:57:40 PST
Message-Id: <347336A4.8BCE6E4@parc.xerox.com>
To: Henrik Frystyk Nielsen <frystyk@w3.org>
Cc: Jeffrey Mogul <mogul@pa.dec.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4737
"accept-" request headers are handled specially by the 'vary'
header response. Since this doesn't apply end-to-end and might
be introduced by an intermediate, I don't think that it should
be called "Accept-" anything. Roy's suggestion of making this
an option to 'Connection' might be reasonable, but I'm suspicious
of adding this last-minute feature into a Draft Standard.

Is there some way that having compression transfer encodings
as opposed to compression content-encodings could be
handled outside of the main HTTP draft, and moved forward
as a separate Proposed (or even Experimental) standard?

Received on Wednesday, 19 November 1997 11:03:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:21 UTC