Currently the WebDAV protocol is a standard, and we have it available by default in all desktop operating systems such as Windows, Linux and also macOS. There are different WebDAV clients for different operating systems, they are more or less features. The information that is stored in these custom properties depends on the WebDAV client, but the new WebDAV module allows publishing clients to save these properties to a simple property store for later retrieval. This document walks you through configuring the new WebDAV module to store custom properties, which are used by some WebDAV clients.
| Communication protocol | |
| OSI layer | Application |
|---|---|
| Port(s) | 80, 443 |
| RFC(s) | RFC 2518, RFC4918 |
| Website | www.webdav.org |
WebDAV (Web Distributed Authoring and Versioning) is an extension of the Hypertext Transfer Protocol (HTTP) that allows clients to perform remote Web content authoring operations. WebDAV is defined in RFC4918 by a working group of the Internet Engineering Task Force.
The WebDAV1 protocol provides a framework for users to create, change and move documents on a server. The most important features of the WebDAV protocol include the maintenance of properties about an author or modification date, namespace management, collections, and overwrite protection. Maintenance of properties includes such things as the creation, removal, and querying of file information. Namespace management deals with the ability to copy and move web pages within a server's namespace. Collections deal with the creation, removal, and listing of various resources. Lastly, overwrite protection handles aspects related to locking of files.
Many modern operating systems provide built-in client-side support for WebDAV.
Best Webdav Client 2020
History[edit]
WebDAV began in 1996 when Jim Whitehead, a PhD graduate from UC Irvine, worked with the World Wide Web Consortium (W3C) to host two meetings to discuss the problem of distributed authoring on the World Wide Web with interested people.[1][2]Tim Berners-Lee's original vision of the Web involved a medium for both reading and writing. In fact, Berners-Lee's first web browser, called WorldWideWeb, could both view and edit web pages; but, as the Web grew, it became a read-only medium for most users. Whitehead and other like-minded people wanted to transcend that limitation.[3]
The meetings resulted in the formation of an IETF working group, because the new effort would lead to extensions to HTTP, which the IETF had started to standardize.
As work began on the protocol, it became clear that handling both distributed authoring and versioning together would involve too much work and that the tasks would have to be separated. The WebDAV group focused on distributed authoring, and left versioning for the future. (The Delta-V extension added versioning later – see the Extensions section below.)
The WebDAV working group concluded its work in March 2007, after the Internet Engineering Steering Group (IESG) accepted an incremental update to RFC2518. Other extensions left unfinished at that time, such as the BIND method, have been finished by their individual authors, independent of the formal working group.
Implementation[edit]
WebDAV extends the set of standard HTTP verbs and headers allowed for request methods. The added verbs include:
- COPY
- copy a resource from one URI to another
- LOCK
- put a lock on a resource. WebDAV supports both shared and exclusive locks.
- MKCOL
- create collections (a.k.a. a directory)
- MOVE
- move a resource from one URI to another
- PROPFIND
- retrieve properties, stored as XML, from a web resource. It is also overloaded to allow one to retrieve the collection structure (also known as directory hierarchy) of a remote system.
- PROPPATCH
- change and delete multiple properties on a resource in a single atomic act
- UNLOCK
- remove a lock from a resource
Server support[edit]
- Apache HTTP Server provides WebDAV modules based on both davfs and Apache Subversion (svn).
- Caddy has an optional WebDAV module[4]
- lighttpd has an optional WebDAV module[5]
- Mailfence offers WebDAV support through a virtual drive+ you can connect exterrnal drives to Mailfence Documents[6]
- Microsoft's IIS has a WebDAV module.
- MyWorkDrive Server supports WebDAV for accessing files via IIS module.[7]
- Nextcloud is a fork of ownCloud, and therefore also offers full WebDAV support[8]
- Nginx has a very limited optional WebDAV module[9] and a third-party module[10]
- ownCloud is a cloud storage PHP application which offers full WebDAV support[11]
- SabreDAV is a PHP application that can be used on Apache or Nginx in lieu of their bundled modules
Client support[edit]
- Git supports writing to HTTP remotes, although the 'smart' Git protocol for HTTP requiring special server support was made the preferred protocol over WebDAV
- Linux via GVfs, including GNOME Files and via KIO, including Konqueror and Dolphin
- macOS, including native support for CalDAV and CardDAV, the design of which is based on WebDAV
- Microsoft Windows, including native support in Explorer
Documents produced by the working group[edit]
The WebDAV working group produced several works:
- a requirements document: 'Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web' RFC2291, issued February 1998
- a base protocol document (excluding versioning, despite its title): 'HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)' RFC4918, issued June 2007 (which updates and supersedes 'HTTP Extensions for Distributed Authoring – WebDAV' RFC2518, issued February 1999)
- the ordered collections protocol: 'Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol' RFC3648, issued December 2003
- the access control protocol: 'Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol' RFC3744, issued May 2004
- a quota specification: 'Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections' RFC4331, issued February 2006
- a redirect specification: 'Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources' RFC4437, issued March 2006
Other documents published through IETF[edit]
- the versioning protocol: 'Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)' RFC3253 (created by the Delta-V working group)
- a specification of WebDAV property datatypes: 'Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties' RFC4316
- a document defining how to initiate mounting of a WebDAV resource: 'Mounting Web Distributed Authoring and Versioning (WebDAV) Servers' RFC4709
- a calendar access protocol: 'Calendaring Extensions to WebDAV (CalDAV)' RFC4791
- a query protocol: 'Web Distributed Authoring and Versioning (WebDAV) SEARCH' RFC5323
- an extension to the WebDAV ACL specification: 'WebDAV Current Principal Extension' RFC5397
- an extension to the WebDAV MKCOL method: 'Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)' RFC5689
- an extension of the collection model, defining creation and discovery of additional bindings to a resource: 'Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)' RFC5842
- an application of POST to WebDAV collections: 'Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections' RFC5995
- an extension which allows synchronizing large collections efficiently: 'Collection Synchronization for Web Distributed Authoring and Versioning (WebDAV)' RFC6578
Extensions and derivatives[edit]
For versioning, the Delta-V protocol under the Web Versioning and Configuration Management working group adds resource revision tracking, published in RFC3253.
For searching and locating, the DAV Searching and Locating (DASL) working group never produced any official standard although there are a number of implementations of its last draft. Work continued as non-working-group activity.[12] The WebDAV Search specification attempts to pick up where the working group left off, and was published as RFC5323 in November 2008.[13]
For calendaring, CalDAV is a protocol allowing calendar access via WebDAV. CalDAV models calendar events as HTTP resources in iCalendar format, and models calendars containing events as WebDAV collections.
For groupware, GroupDAV is a variant of WebDAV which allows client/server groupware systems to store and fetch objects such as calendar items and address book entries instead of web pages.
For MS Exchange interoperability, WebDAV can be used for reading/updating/deleting items in a mailbox or public folder. WebDAV for Exchange has been extended by Microsoft to accommodate working with messaging data. Exchange Server version 2000, 2003, and 2007 support WebDAV. However, WebDAV support has been discontinued in Exchange 2010[14] in favor of Exchange Web Services (EWS), a SOAP/XML based API.
Additional Windows-specific extensions[edit]
As part of the Windows Server Protocols (WSPP) documentation set,[15] Microsoft published the following protocol documents detailing extensions to WebDAV:
- [MS-WDVME]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions.[16] These extensions include a new verb and new headers, and properties that enable previously unmanageable file types and optimize protocol interactions for file system clients. These extensions introduce new functionality into WebDAV, optimize processing, and eliminate the need for special-case processing.
- [MS-WDV]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions.[17] The client extensions in this specification extend the WebDAV Protocol by introducing new headers that both enable the file types that are not currently manageable and optimize protocol interactions for file system clients. These extensions do not introduce new functionality into the WebDAV Protocol, but instead optimize processing and eliminate the need for special-case processing.
- [MS-WDVSE]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions.[18] The server extensions in this specification extend WebDAV by introducing new HTTP request and response headers that both enable the file types that are not currently manageable and optimize protocol interactions for file system clients. This specification also introduces a new WebDAV method that is used to send search queries to disparate search providers.
- [MS-WEBDAVE]: Web Distributed Authoring and Versioning Error Extensions Protocol Specification.[19] This SharePoint Front-End Protocol describes extended error codes and extended error handling mechanism specified in [MS-WDV] to enable compliant servers to report error condition details on a server response.
Alternatives to WebDAV[edit]
- File Transfer Protocol (FTP), a simple and widely adapted network protocol based on IP, allows users to transfer files between network hosts. FTPS extends FTP for secure traffic.
- SSH File Transfer Protocol (SFTP), an extension of the Secure Shell protocol (SSH) version 2.0, provides secure file-transfer capability ; and scp, a form of SFTP that runs as a single command similar to a regular cp (copy) command in the shell.
- Rsync, a protocol and a command similar to scp, that can also skip rewriting identical files and portions of files, or skip newer files, etc.
- A distributed file system such as the Server Message Block (SMB) protocol allows Microsoft Windows and open-source Samba clients to access and manage files and folders remotely on a suitable file server. Commonly used for multimedia streaming over ethernet and widely supported by Smart TVs.[20]
- AtomPub, an HTTP-based protocol for creating and updating web resources, can be used for some of the use cases of WebDAV. It is based on standard HTTP verbs with standardized collection resources that behave somewhat like the WebDAV model of directories.
- CMIS, a standard consisting of a set of Web services for sharing information among disparate content repositories, seeks to ensure interoperability for people and applications using multiple content repositories; it has both SOAP- and AtomPub-based interfaces
- Wiki software, such as MediaWiki.
- Linked Data Platform (LDP), a Linked Data specification defining a set of integration patterns for building RESTful HTTP services that are capable of read-write of RDF data.
- Object storage such as OpenStack Swift or Amazon S3
See also[edit]
References[edit]
- ^'Proposed agenda for San Mateo Meeting'. 1996.
- ^'Brief mtg. summary'. 1996.
- ^'Re: Updated agenda'.
- ^28 Jul 2017. 'http.webdav - Caddy User Guide'. Retrieved 13 July 2018.
- ^'lighttpd mod webdav'.
- ^'WebDAV implementation of Mailfence'. Retrieved 5 May 2020.
- ^'WebDAV Server Windows'.
- ^'Nextcloud 18 User Manual'. nextcloud.com. Retrieved 22 February 2020.
- ^'Module ngx_http_dav_module'. nginx website. Retrieved 15 July 2016.
- ^'Module nginx-dav-ext-module'. github.com. Retrieved 2 August 2016.
- ^'ownCloud Documentation'. owncloud.com. Retrieved 23 July 2018.
- ^DASLArchived 2004-06-03 at the Wayback Machine
- ^WebDav SEARCH
- ^Discontinued Features: Exchange 2010 SP1 Help Microsoft TechNet
- ^'WSPP – Windows Server Protocols documentation'. 2011.
- ^'MS-WDVME – Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions'. 2014.
- ^'MS-WDV – Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions'. 2011.
- ^'MS-WDVSE – Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions'. 2011.
- ^'MS-WEBDAVE – Web Distributed Authoring and Versioning Error Extensions Protocol Specification'. 2011.
- ^Rau, Thomas (19 October 2017). 'Filme, Musik & Bilder im Heimnetzwerk streamen'. PC-WELT (in German). Retrieved 5 November 2020.
External links[edit]
| Communication protocol | |
| OSI layer | Application |
|---|---|
| Port(s) | 80, 443 |
| RFC(s) | RFC 2518, RFC4918 |
| Website | www.webdav.org |
WebDAV (Web Distributed Authoring and Versioning) is an extension of the Hypertext Transfer Protocol (HTTP) that allows clients to perform remote Web content authoring operations. WebDAV is defined in RFC4918 by a working group of the Internet Engineering Task Force.
The WebDAV1 protocol provides a framework for users to create, change and move documents on a server. The most important features of the WebDAV protocol include the maintenance of properties about an author or modification date, namespace management, collections, and overwrite protection. Maintenance of properties includes such things as the creation, removal, and querying of file information. Namespace management deals with the ability to copy and move web pages within a server's namespace. Collections deal with the creation, removal, and listing of various resources. Lastly, overwrite protection handles aspects related to locking of files.
Many modern operating systems provide built-in client-side support for WebDAV.
Best Webdav Client 2020
History[edit]
WebDAV began in 1996 when Jim Whitehead, a PhD graduate from UC Irvine, worked with the World Wide Web Consortium (W3C) to host two meetings to discuss the problem of distributed authoring on the World Wide Web with interested people.[1][2]Tim Berners-Lee's original vision of the Web involved a medium for both reading and writing. In fact, Berners-Lee's first web browser, called WorldWideWeb, could both view and edit web pages; but, as the Web grew, it became a read-only medium for most users. Whitehead and other like-minded people wanted to transcend that limitation.[3]
The meetings resulted in the formation of an IETF working group, because the new effort would lead to extensions to HTTP, which the IETF had started to standardize.
As work began on the protocol, it became clear that handling both distributed authoring and versioning together would involve too much work and that the tasks would have to be separated. The WebDAV group focused on distributed authoring, and left versioning for the future. (The Delta-V extension added versioning later – see the Extensions section below.)
The WebDAV working group concluded its work in March 2007, after the Internet Engineering Steering Group (IESG) accepted an incremental update to RFC2518. Other extensions left unfinished at that time, such as the BIND method, have been finished by their individual authors, independent of the formal working group.
Implementation[edit]
WebDAV extends the set of standard HTTP verbs and headers allowed for request methods. The added verbs include:
- COPY
- copy a resource from one URI to another
- LOCK
- put a lock on a resource. WebDAV supports both shared and exclusive locks.
- MKCOL
- create collections (a.k.a. a directory)
- MOVE
- move a resource from one URI to another
- PROPFIND
- retrieve properties, stored as XML, from a web resource. It is also overloaded to allow one to retrieve the collection structure (also known as directory hierarchy) of a remote system.
- PROPPATCH
- change and delete multiple properties on a resource in a single atomic act
- UNLOCK
- remove a lock from a resource
Server support[edit]
- Apache HTTP Server provides WebDAV modules based on both davfs and Apache Subversion (svn).
- Caddy has an optional WebDAV module[4]
- lighttpd has an optional WebDAV module[5]
- Mailfence offers WebDAV support through a virtual drive+ you can connect exterrnal drives to Mailfence Documents[6]
- Microsoft's IIS has a WebDAV module.
- MyWorkDrive Server supports WebDAV for accessing files via IIS module.[7]
- Nextcloud is a fork of ownCloud, and therefore also offers full WebDAV support[8]
- Nginx has a very limited optional WebDAV module[9] and a third-party module[10]
- ownCloud is a cloud storage PHP application which offers full WebDAV support[11]
- SabreDAV is a PHP application that can be used on Apache or Nginx in lieu of their bundled modules
Client support[edit]
- Git supports writing to HTTP remotes, although the 'smart' Git protocol for HTTP requiring special server support was made the preferred protocol over WebDAV
- Linux via GVfs, including GNOME Files and via KIO, including Konqueror and Dolphin
- macOS, including native support for CalDAV and CardDAV, the design of which is based on WebDAV
- Microsoft Windows, including native support in Explorer
Documents produced by the working group[edit]
The WebDAV working group produced several works:
- a requirements document: 'Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web' RFC2291, issued February 1998
- a base protocol document (excluding versioning, despite its title): 'HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)' RFC4918, issued June 2007 (which updates and supersedes 'HTTP Extensions for Distributed Authoring – WebDAV' RFC2518, issued February 1999)
- the ordered collections protocol: 'Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol' RFC3648, issued December 2003
- the access control protocol: 'Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol' RFC3744, issued May 2004
- a quota specification: 'Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections' RFC4331, issued February 2006
- a redirect specification: 'Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources' RFC4437, issued March 2006
Other documents published through IETF[edit]
- the versioning protocol: 'Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)' RFC3253 (created by the Delta-V working group)
- a specification of WebDAV property datatypes: 'Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties' RFC4316
- a document defining how to initiate mounting of a WebDAV resource: 'Mounting Web Distributed Authoring and Versioning (WebDAV) Servers' RFC4709
- a calendar access protocol: 'Calendaring Extensions to WebDAV (CalDAV)' RFC4791
- a query protocol: 'Web Distributed Authoring and Versioning (WebDAV) SEARCH' RFC5323
- an extension to the WebDAV ACL specification: 'WebDAV Current Principal Extension' RFC5397
- an extension to the WebDAV MKCOL method: 'Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)' RFC5689
- an extension of the collection model, defining creation and discovery of additional bindings to a resource: 'Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)' RFC5842
- an application of POST to WebDAV collections: 'Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections' RFC5995
- an extension which allows synchronizing large collections efficiently: 'Collection Synchronization for Web Distributed Authoring and Versioning (WebDAV)' RFC6578
Extensions and derivatives[edit]
For versioning, the Delta-V protocol under the Web Versioning and Configuration Management working group adds resource revision tracking, published in RFC3253.
For searching and locating, the DAV Searching and Locating (DASL) working group never produced any official standard although there are a number of implementations of its last draft. Work continued as non-working-group activity.[12] The WebDAV Search specification attempts to pick up where the working group left off, and was published as RFC5323 in November 2008.[13]
For calendaring, CalDAV is a protocol allowing calendar access via WebDAV. CalDAV models calendar events as HTTP resources in iCalendar format, and models calendars containing events as WebDAV collections.
For groupware, GroupDAV is a variant of WebDAV which allows client/server groupware systems to store and fetch objects such as calendar items and address book entries instead of web pages.
For MS Exchange interoperability, WebDAV can be used for reading/updating/deleting items in a mailbox or public folder. WebDAV for Exchange has been extended by Microsoft to accommodate working with messaging data. Exchange Server version 2000, 2003, and 2007 support WebDAV. However, WebDAV support has been discontinued in Exchange 2010[14] in favor of Exchange Web Services (EWS), a SOAP/XML based API.
Additional Windows-specific extensions[edit]
As part of the Windows Server Protocols (WSPP) documentation set,[15] Microsoft published the following protocol documents detailing extensions to WebDAV:
- [MS-WDVME]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions.[16] These extensions include a new verb and new headers, and properties that enable previously unmanageable file types and optimize protocol interactions for file system clients. These extensions introduce new functionality into WebDAV, optimize processing, and eliminate the need for special-case processing.
- [MS-WDV]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions.[17] The client extensions in this specification extend the WebDAV Protocol by introducing new headers that both enable the file types that are not currently manageable and optimize protocol interactions for file system clients. These extensions do not introduce new functionality into the WebDAV Protocol, but instead optimize processing and eliminate the need for special-case processing.
- [MS-WDVSE]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions.[18] The server extensions in this specification extend WebDAV by introducing new HTTP request and response headers that both enable the file types that are not currently manageable and optimize protocol interactions for file system clients. This specification also introduces a new WebDAV method that is used to send search queries to disparate search providers.
- [MS-WEBDAVE]: Web Distributed Authoring and Versioning Error Extensions Protocol Specification.[19] This SharePoint Front-End Protocol describes extended error codes and extended error handling mechanism specified in [MS-WDV] to enable compliant servers to report error condition details on a server response.
Alternatives to WebDAV[edit]
- File Transfer Protocol (FTP), a simple and widely adapted network protocol based on IP, allows users to transfer files between network hosts. FTPS extends FTP for secure traffic.
- SSH File Transfer Protocol (SFTP), an extension of the Secure Shell protocol (SSH) version 2.0, provides secure file-transfer capability ; and scp, a form of SFTP that runs as a single command similar to a regular cp (copy) command in the shell.
- Rsync, a protocol and a command similar to scp, that can also skip rewriting identical files and portions of files, or skip newer files, etc.
- A distributed file system such as the Server Message Block (SMB) protocol allows Microsoft Windows and open-source Samba clients to access and manage files and folders remotely on a suitable file server. Commonly used for multimedia streaming over ethernet and widely supported by Smart TVs.[20]
- AtomPub, an HTTP-based protocol for creating and updating web resources, can be used for some of the use cases of WebDAV. It is based on standard HTTP verbs with standardized collection resources that behave somewhat like the WebDAV model of directories.
- CMIS, a standard consisting of a set of Web services for sharing information among disparate content repositories, seeks to ensure interoperability for people and applications using multiple content repositories; it has both SOAP- and AtomPub-based interfaces
- Wiki software, such as MediaWiki.
- Linked Data Platform (LDP), a Linked Data specification defining a set of integration patterns for building RESTful HTTP services that are capable of read-write of RDF data.
- Object storage such as OpenStack Swift or Amazon S3
See also[edit]
References[edit]
- ^'Proposed agenda for San Mateo Meeting'. 1996.
- ^'Brief mtg. summary'. 1996.
- ^'Re: Updated agenda'.
- ^28 Jul 2017. 'http.webdav - Caddy User Guide'. Retrieved 13 July 2018.
- ^'lighttpd mod webdav'.
- ^'WebDAV implementation of Mailfence'. Retrieved 5 May 2020.
- ^'WebDAV Server Windows'.
- ^'Nextcloud 18 User Manual'. nextcloud.com. Retrieved 22 February 2020.
- ^'Module ngx_http_dav_module'. nginx website. Retrieved 15 July 2016.
- ^'Module nginx-dav-ext-module'. github.com. Retrieved 2 August 2016.
- ^'ownCloud Documentation'. owncloud.com. Retrieved 23 July 2018.
- ^DASLArchived 2004-06-03 at the Wayback Machine
- ^WebDav SEARCH
- ^Discontinued Features: Exchange 2010 SP1 Help Microsoft TechNet
- ^'WSPP – Windows Server Protocols documentation'. 2011.
- ^'MS-WDVME – Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions'. 2014.
- ^'MS-WDV – Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions'. 2011.
- ^'MS-WDVSE – Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions'. 2011.
- ^'MS-WEBDAVE – Web Distributed Authoring and Versioning Error Extensions Protocol Specification'. 2011.
- ^Rau, Thomas (19 October 2017). 'Filme, Musik & Bilder im Heimnetzwerk streamen'. PC-WELT (in German). Retrieved 5 November 2020.
External links[edit]
The following tables list and compare general information for a number of WebDAV clients and WebDAV libraries. Please see the individual products' articles for further information.
WebDAV clients (outdated)[edit]
| Client | Creator | Operating system support | Latest stable version | License | Interface |
|---|---|---|---|---|---|
| Cyberduck | David V. Kocher | Windows, MacOSX | 7.02 — 2019/07/25 [1] | GPL | GUI |
| davfs | GNOME team | FUSE | 1.5.4 — 2016/04/16 | GPL | VFS |
| davix | CERN | Windows, Linux, MacOSX | 0.7.4. — 2019/07/04 [2] | LGPL | CLI |
| GVfs | GNOME team | GNOME | 40.0[3] (24 March 2021; 46 days ago) [±] | GPL | VFS |
| KIO | KDE team | KDE | 4.14.38 (November 7, 2017; 3 years ago) [±][4] | GPL | VFS |
| Konqueror | KDE team | KDE | 4.14.38 (November 7, 2017; 3 years ago) [±][5] | GPL | GUI |
| GNOME Files | GNOME team | GNOME | 40.0[6] (24 March 2021; 46 days ago) [±] | GPL | GUI |
| SmartFTP | SmartSoft Ltd | Windows | 9.0.2626 — 2019/01/16 | Proprietary | GUI |
| WebDrive | South River Technologies | Windows, OS X, iOS, Droid | 2019 — 2019/02/09 [7] | Proprietary | VFS |
| WinSCP | Martin Přikryl | Windows | 5.15.3 — 2019/07/21 [8] | GPL | CLI and GUI |
WebDAV libraries[edit]
| Libraries | Creator | Operating system or platform | Latest stable version | License | Language |
|---|---|---|---|---|---|
| Apache Wink | Apache Software foundation | JVM | Java | ||
| Apache Tomcat | Apache Software foundation | JVM | Java | ||
| Apache Jackrabbit | Apache Software foundation | JVM | 2.14.0 2017/01/06 | ASF | Java |
| neon (library) | Joe Orton | Linux, MacOSX | 0.30.2 2016/09/30 | LGPL | C |
| sabre/dav | fruux | Windows, Linux, MacOSX | 3.2 2016/06/27 | New BSD | PHP |
See also[edit]
References[edit]
Best Webdav Client Software
- ^https://cyberduck.io/changelog/ Retrieved 5 August 2019
- ^https://dmc.web.cern.ch/projects/davix/home Retrieved 5 August 2019
- ^Clasen, Matthias (24 March 2021). 'GNOME 40 released'. GNOME Mail Services (Mailing list). Retrieved 29 March 2021.
- ^'KDE Ships KDE Applications and Platform 4.14.3'. KDE. 11 November 2014. Retrieved 13 November 2015.
- ^'KDE Ships KDE Applications and Platform 4.14.3'. KDE. 11 November 2014. Retrieved 13 November 2015.
- ^Clasen, Matthias (24 March 2021). 'GNOME 40 released'. GNOME Mail Services (Mailing list). Retrieved 29 March 2021.
- ^https://webdrive.com/wd-support/release-notes/ Retrieved 5 August 2019
- ^https://winscp.net/eng/docs/history#5.15.3 Retrieved 5 August 2019
Best Free Webdav Client
