- From: Greg Stein <gstein@lyra.org>
- Date: Tue, 19 Mar 2002 05:16:39 -0800
- To: Julian Reschke <julian.reschke@greenbytes.de>, "Sohn, Matthias" <matthias.sohn@sap.com>
- Cc: ietf-dav-versioning@w3.org, w3c-dist-auth@w3.org
On Tue, Mar 19, 2002 at 10:58:32AM +0100, Julian Reschke wrote: > > [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Sohn, Matthias >... > > is it possible to specify extension features (that are not defined in the > > DeltaV spec) in the response to a OPTIONS request ? > > It's possible, but I would strongly recommend not to do that. > > If you need a non-intrusive way to signal server extensions, use a custom > live property. There was some amount of consensus a while back on the DAV WG list that the DAV: header should allow Coded-URLs in it. mod_dav took this approach, so an OPTIONS response looks like: HTTP/1.1 200 OK Date: Tue, 19 Mar 2002 13:10:17 GMT Server: Apache/1.3.19 (Unix) DAV/1.0.2 Content-Length: 0 MS-Author-Via: DAV Allow: OPTIONS, GET, HEAD, POST, DELETE, TRACE, PROPFIND, PROPPATCH, COPY, MOVE, LOCK, UNLOCK DAV: 1,2,<http://apache.org/dav/propset/fs/1> Connection: close Content-Type: text/plain Cheers, -g -- Greg Stein, http://www.lyra.org/
Received on Tuesday, 19 March 2002 08:13:10 UTC