Next message: Geoffrey M. Clemm: "RE: Versioning TeleConf Agenda, 6/19/00 (Monday) 2pm-3pm EST [resend]"
Date: Sun, 25 Jun 2000 16:33:23 -0400 (EDT)
Message-Id: <200006252033.QAA02400@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: [Moderator Action] draft-ietf-deltav-versioning-04.8
I believe it is unlikely that a proxy will cache the results of an
unknown method. Or put a different way, does anyone know of a proxy
that would cache the results of an unknown method?
Cheers,
Geoff
From: Joe Meadows <joe.meadows@boeing.com> (by way of "Ralph R. Swick" <swick@w3.org>)
The current draft appears to assume that compliant clients are talking
directly to compliant servers. However, some consideration may need to
be given to its use through either HTTP/1.1 or HTTP/1.0 proxies.
For instance, several of the methods provide responses that are not
supposed to be cached; i.e.
"A CHECKOUT response MUST NOT be cached."
It would probably be helpful to have examples that explicitly set
the appropriate HTTP headers to make sure that responses aren't cached
(i.e. by delta-V unaware proxies).
>>REQUEST
CHECKOUT /foo.html HTTP/1.1
Host: www.webdav.org
Content-Length: 0
>>RESPONSE
HTTP/1.1 200 Ok
Cache-Control: no-cache
Pragma: no-cache <--- maybe??
Location: http://www.webdav.org/ws/core/3/foo.html
I haven't been following this activity, so sorry if I've missed something
obvious.
Cheers,
Joe Meadows