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

Re: draft-holtman-http-safe-01.txt

From: Koen Holtman <koen@win.tue.nl>
Date: Thu, 20 Mar 1997 19:08:32 +0100 (MET)
Message-Id: <199703201808.TAA17760@wsooti08.win.tue.nl>
To: mcmanus@appliedtheory.com
Cc: dwm@xpasc.com, http-wg@cuckoo.hpl.hp.com
Patrick McManus:
>
>That's not how I read section 3:
>
>--
>3 The Safe response header
>
> This header is proposed as an addition to the HTTP/1.x suite.
>
> The Safe response header field indicates whether the corresponding
> request is safe in the sense of Section 9.1.1 (Safe Methods) of the
> HTTP/1.1 draft specification [1].
>--
>
>It speaks very specifically that the safe response header field talks
>about the corresponding (i.e. current) request.. I think making any
>assumptions about future request/response pairs requires clairvoyance

For the record, your interpretation is not what I meant to say when I wrote
the above definition of Safe.  `the request is safe' means that it is always
safe.

>(and the Note further in section three claims that it can do this
>clairvoyance)

...and the note further in the section should have alerted you that you
were misreading the definition.

>-Patrick

Koen.
Received on Thursday, 20 March 1997 10:10:40 EST

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