headers
Arnaud Quillaud | 8 Aug 2007 18:06
Picon

PROPFIND/REPORT on non existing resource/collection


Hello,

When issuing a PROPFIND or REPORT with a Request URI that does not exist, what should be returned:
- a 404 Not Found ?
- or a 207 multistatus containing a single response + href + status = 404 (e.g.
<DAV:response><DAV:href>/toto/≤/DAV:href><DAV:status>404 Not
Found</DAV:status></DAV:response>) ?

The only indication that I have found comes from the REPORT method definition where it is stated
(http://tools.ietf.org/html/rfc3253#section-3.6): "If a Depth request header is included, the
response MUST be a 207 Multi-Status.".

Thanks,

Arnaud Q
Permalink | Reply | 1 comment |
headers
Arnaud Quillaud | 8 Aug 2007 18:30
Picon

conditional methods and WebDAV


Hello,

HTTP defines a few conditional headers (if-* headers) and so does WebDAV (if header). In both cases those
headers can be used "to make *a* method conditional". There is no table listing which method can be made conditional.
By reading between the lines one can guess that the if-* headers main purpose is for GET/PUT methods while if
can be applied to pretty much any method but that is about it.

This brings up a few questions:
* is the choice to make one method conditional or not left to server implementations ?
* how can a client discover whether a particular method honor one of the if* headers (e.g. DELETE with
if-match, PROPPATCH with if-unmodified-since or PROPFIND with if-modified-since) ?
* should the WebDAV if header be honored on all HTTP/WebDAV/*DAV methods ?

Thanks,

Arnaud Q
Permalink | Reply | 2 comments |
headers
Kevin Wiggen | 8 Aug 2007 18:55
Favicon

RE: conditional methods and WebDAV


It is my understanding that to be a HTTP compliant server the server
MUST honor the if header on ALL methods (including Webdav).

The open issue IMHO is, does the IF header relate to just the URI, or
does it relate to every resource the method touches (DEPTH infinity or a
DELETE can touch LOTS of objects for instance).  I do not remember if
this was ever decided (its been a while) but I would bet this could
behave differently depending on the server.

Kevin

-----Original Message-----
From: w3c-dist-auth-request <at> w3.org [mailto:w3c-dist-auth-request <at> w3.org]
On Behalf Of Arnaud Quillaud
Sent: Wednesday, August 08, 2007 9:30 AM
To: w3c-dist-auth <at> w3.org
Subject: conditional methods and WebDAV

Hello,

HTTP defines a few conditional headers (if-* headers) and so does WebDAV
(if header). In both cases those headers can be used "to make *a* method
conditional". There is no table listing which method can be made
conditional.
By reading between the lines one can guess that the if-* headers main
purpose is for GET/PUT methods while if can be applied to pretty much
any method but that is about it.

This brings up a few questions:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Julian Reschke | 8 Aug 2007 22:11
Picon
Picon

Re: PROPFIND/REPORT on non existing resource/collection


Arnaud Quillaud wrote:
> Hello,
> 
> When issuing a PROPFIND or REPORT with a Request URI that does not exist, what should be returned:
> - a 404 Not Found ?

Yes.

> - or a 207 multistatus containing a single response + href + status = 404 (e.g.
<DAV:response><DAV:href>/toto/≤/DAV:href><DAV:status>404 Not
Found</DAV:status></DAV:response>) ?

Should be equivalent.

> The only indication that I have found comes from the REPORT method definition where it is stated
(http://tools.ietf.org/html/rfc3253#section-3.6): "If a Depth request header is included, the
response MUST be a 207 Multi-Status.".

I guess we need to clarify that when we move REPORT into a separate spec.

Best regards, Julian
Permalink | Reply | 0 comments |
headers
Julian Reschke | 8 Aug 2007 22:13
Picon
Picon

Re: conditional methods and WebDAV


Arnaud Quillaud wrote:
> Hello,
> 
> HTTP defines a few conditional headers (if-* headers) and so does WebDAV (if header). In both cases those
headers can be used "to make *a* method conditional". There is no table listing which method can be made conditional.
> By reading between the lines one can guess that the if-* headers main purpose is for GET/PUT methods while
if can be applied to pretty much any method but that is about it.

Yes.

> This brings up a few questions:
> * is the choice to make one method conditional or not left to server implementations ?

Not really.

> * how can a client discover whether a particular method honor one of the if* headers (e.g. DELETE with
if-match, PROPPATCH with if-unmodified-since or PROPFIND with if-modified-since) ?
> * should the WebDAV if header be honored on all HTTP/WebDAV/*DAV methods ?

I'd say it should apply to all methods, but I'd be surprised if all 
servers get this right. See also current discussion over on the HTTP-WG 
mailing list about entity tags and methods such as PROPFIND/PROPPATCH.

Best regards, Julian
Permalink | Reply | 1 comment |
headers
Jack Bates | 11 Aug 2007 00:42
Picon
Favicon

versions

How can I use WebDAV to discover multiple versions of a resource, such
as different content types or dimensions?

I contributed a WebDAV module to the Gallery open source project:
http://codex.gallery2.org/WebDAV

Recently I have worked on a WebDAV module for MediaWiki, implementing
DeltaV and DASL: http://www.mediawiki.org/wiki/

Organizations where I've installed Gallery and MediaWiki frequently
integrate these projects with a Drupal CMS installation, so I'm writing
a Drupal widget for creating links in Drupal "node" bodies to WebDAV
resources.

The first challenge is: the Gallery WebDAV interface was intended for
file system applications, so resource hrefs currently access Gallery
"item" content, e.g. full size JPEG, PDF or AVI:
http://freegeekvancouver.org/en/w/docs/fgv-startup_brochurev2.pdf

I want links created by my widget to instead access an HTML interface to
the resource:
http://freegeekvancouver.org/en/v/docs/fgv-startup_brochurev2.pdf.html

I understand that according to REST principles, the content type of the
resource should not be included in its URI, that the Accept: request
header should be used instead. So I guess an Accept: value of text/html
could be used to access an HTML interface to the resource. Still, I have
two problems:

1) Widget should let users choose which version of the resource
(Continue reading)

Permalink | Reply | 1 comment |
headers
Julian Reschke | 17 Aug 2007 14:26
Picon
Picon

Re: versions


Jack Bates wrote:
> How can I use WebDAV to discover multiple versions of a resource, such
> as different content types or dimensions?

I don't think we have a solution for that.

> I contributed a WebDAV module to the Gallery open source project:
> http://codex.gallery2.org/WebDAV
> 
> Recently I have worked on a WebDAV module for MediaWiki, implementing
> DeltaV and DASL: http://www.mediawiki.org/wiki/

That sounds like a very cool project.

Comment wrt to <http://www.mediawiki.org/wiki/WebDAV>: WebDAV is now 
defined in RFC4918.

> Organizations where I've installed Gallery and MediaWiki frequently
> integrate these projects with a Drupal CMS installation, so I'm writing
> a Drupal widget for creating links in Drupal "node" bodies to WebDAV
> resources.
> 
> The first challenge is: the Gallery WebDAV interface was intended for
> file system applications, so resource hrefs currently access Gallery
> "item" content, e.g. full size JPEG, PDF or AVI:
> http://freegeekvancouver.org/en/w/docs/fgv-startup_brochurev2.pdf
> 
> I want links created by my widget to instead access an HTML interface to
> the resource:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tim Olsen | 21 Aug 2007 20:42

Is it ok to create a derivate of the webdav logo?


Hello,

The company I work for, Lime Spot, will be launching a website soon to
host one of our open-source, webdav-related projects (with more projects
to come later). I'm thinking of having one of our graphic designers
create a logo for the site that would be a cross between the Lime Group
logo (The non-textual part of http://www.limegroup.com/img/logo.gif)
and the WebDAV logo (http://www.webdav.org/images/webdav-logo.jpg).

Would people be ok with our creating and using a logo that was a
derivative of the webdav logo?

Thanks,
Tim Olsen
Permalink | Reply | 0 comments |

Gmane