Re: New "200 OK" status codes, PATCH & PROPFIND

On mån, 2007-08-06 at 23:43 +0200, Julian Reschke wrote:

> Cache-Control applies to the response. What the proposal is about is to 
> enable the server to say that
> 
> (a) the response body (DAV:multistatus) is cachable for n seconds, while
> 
> (b) the substitute URL can be used for N seconds,

Is there really a need to time-limit the substitute URL?

Imho this should be to an permanent alternative URL-namespace for
accessing the properties, existing even before the request has been
seen. If the URI disappeares for whatever reason the client will need to
fall back on PROPFIND, or whatever method is used in future to find the
"PROPFIND URI namespace schema".

There is no problem for PROPFIND to define that this Content-Location is
permanent.

There is also no problem for PROPFIND to define that result may be
cached on that URI without first issuing a GET under restricted
conditions (i.e. at least same host as in the Request-URI) even if I
would advice some caution there to avoid cache pollution security
issues, and would therefore recommend to only allow the end-client to
cache the entity for the purpose of PROPFIND alone, not "non-PROPFIND"
GET's for the same URI (note: the restriction on host is then not
needed).

Regards
Henrik