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

draft-ieft-http-options-00.txt

From: Dave Kristol <dmk@research.bell-labs.com>
Date: Thu, 7 Aug 97 15:06:10 EDT
Message-Id: <9708071906.AA24943@zp>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
I read through the I-D, thinking about how an origin server that
supports cookies (i.e., RFC 2109) might respond to

	OPTIONS * HTTP/1.1
	Compliance: rfc=2109

The problem is that (I believe) most of the support is not in the
server itself, but in CGIs.  Consequently, the server software may not
be able to answer authoritatively about whether RFC 2109 is supported,
because that may depend on what each individual CGI does.

What advice would the authors (or others) give?

Nit:  p.4, section 3.2:  I think the phrase "originating sender" is
a poor one.  From one perspective, the originating sender is the
client that initiated the request.  But I think it's intended to mean
the server that responded to the OPTIONS method.

Dave Kristol
Received on Thursday, 7 August 1997 12:29:39 EDT

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