My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
RFCs  
List of related RFCs and implementation status
Updated May 11, 2012 by evert...@gmail.com

RFCs

RFC2617 HTTP Basic/Digest auth Implemented
RFC2518 Old WebDAV specification Implemented
RFC4311 Quota and Size Properties Implemented
RFC4709 Mounting WebDAV servers Implemented
RFC4918 Current WebDAV rfc Implemented
RFC5789 PATCH method for HTTP Implemented
RFC3744 ACL Mostly implemented
RFC4791 CalDAV Mostly Implemented
RFC5397 Current-Principal Implemented
RFC5689 Extended MKCOL Implemented
RFC4437 Redirects Reference Resources Future
RFC3253 Delta-V extension Not planned
RFC3648 Ordered collections Not planned
RFC5323 WebDAV SEARCH Not planned

Drafts

draft-ietf-webdav-bind-latest Bindings/symbolic links Maybe
draft-daboo-et-al-icalendar-in-xml ICalendar representation in XML Future
draft-ietf-vcarddav-carddav CardDAV Mostly implemented
draft-daboo-carddav-directory-gateway CardDAV Directory Implemented

Proprietary

caldav-ctag CalDAV Collection Entity tag (CTag) in CalDAV Implemented
caldav-proxy CalDAV Proxy (calendar delegation) Implemented

Related RFC's

RFC Name Description Required by
RFC4790 Collation Registry substring matching (i;octet and i;ascii-casemap collation support) RFC4791
RFC5545 iCalendar 2.0 Calendar object format RFC4791

Comment by D.A.Bori...@gmail.com, Feb 7, 2010

Please add support CardDAV.

Comment by project member evert...@gmail.com, Feb 7, 2010

Added CardDAV to the list. Would be nice to have at one point; CalDAV is first though.

Comment by Playful...@gmail.com, Jul 9, 2011

Firstly awesome job, you guys are doing. This is the most complete WedDav? solution i have seen. I look forward to it evolving into a full blown product with proper admin screens.

Can you tell me, how much support for RFC3744 there is in the current version, and what the roadmap is for further support?

I can see that there are still outstanding issuses with the RFC and it has still not been standarised.

When connecting through say windows, will the RFC3744 support in SabreDav? be respected and restrict individuals/groups?

Also another thing that just sprung to mind. Is there a way of adding a captcha to prevent web attacks? What is there stopping a brut force attack of a webdav server?

regards

Comment by project member evert...@gmail.com, Jul 9, 2011

RFC3744 support is decent. A lot of features are implemented, which should allow you to do most stuff you need for ACL. Things like 'deny' rules aren't supported yet, but they will come if their needed.

However, SabreDAV remains primarily a library to do WebDAV things. One of the things this implies is that an Admin interface may not come, just not part of the goals currently. In the case of ACL, you will need to implement this yourself by extending File/Directory classes and adding methods from the Sabre_DAVACL_IACL interface.

Keep in mind though that most standard WebDAV clients don't support RFC3744. While operations will be denied, this may not be reflected well in your WebDAV client of choice, and may even break.

As for your last question, the best way to prevent any type of brute force attacks, is probably to implement logging-in throttling. You'd currently do that by creating your own Auth backend, and implement that there. Any sort of captcha would not be supported by clients.


Sign in to add a comment
Powered by Google Project Hosting