WebDAV started life when Jim Whitehead convinced the W3C to host two meetings where people interested in the problem of distributed authoring on the World Wide Web could get together to discuss possible solutions.
As work began on the protocol it became clear that handling both distributed authoring and versioning was just too much and that the tasks would have to be separated.
The WebDAV working group is still working on a number of extensions to WebDAV including - bindings, and on progressing the base specification to the next maturity level in the Internet Standards track.
For example, if the resource with URL http://foo.com/bar/blah is not WebDAV compliant and the URL http://foo.com/bar/ identifies a collection then URL http://foo.com/bar/blah may or may not be an internal member of the collection with URL http://foo.com/bar/.
On WebDAV compliant servers the URI of the source resource(s) may be stored in a link on the output resource with type DAV:source (see section 13.10 for a description of the source link property).
WebDAV clients can be good citizens by using a lock / retrieve / write /unlock sequence of operations (at least by default) whenever they interact with a WebDAVserver that supports locking.
WebDAV is an ambitious effort to create a standard for collaborative authoring that includes locks and authentication.
The stated goal of the WebDAV working group was (from the charter) to "define the HTTPextensions necessary to enable distributed web authoring tools to be broadly interoperable, while supporting user needs", and in this respect DAV is completing the original vision of the Web as a writeable, collaborative medium [13].
Whether WebDAV will have an obsoleting impact on the currently dominating technologies like FTP and CVS (like it had on gopher, for example) or if it's just another case of reinventing the wheel remains to be seen.
WebDAV clients are native to Windows XP, Mac OS X, etc., and one can, therefore, simply mount a drive from one of these operating systems to one or several remote embedded devices.
WebDAV eliminates the typical problems encountered in a mixed UNIX/Windows environment where a Windows machine cannot mount a NFS drive and vice versa.
Standards Track [Page 14] RFC 2518 WEBDAV February 1999 However, there are times when the goal of a lock is not to exclude others from exercising an access right but rather to provide a mechanism for principals to indicate that they intend to exercise their access rights.
Standards Track [Page 24] RFC 2518 WEBDAV February 1999 In the case of allprop and propname, if a principal does not have the right to know whether a particular property exists then the property should be silently excluded from the response.
Standards Track [Page 41] RFC 2518 WEBDAV February 1999 8.9 MOVE Method The MOVE operation on a non-collection resource is the logical equivalent of a copy (COPY), followed by consistency maintenance processing, followed by a delete of the source, where all three actions are performed atomically.
WebDAV is not supported in Windows NT 4.0 and therefore could not be used as an attack vector, and both Windows NT 4.0 and Windows XP do not install IIS by default.
WebDAV is an industry standard extension to the HTTP specification.
Although WebDAV is supported in IIS 5.1 if it is installed by a user, the underlying Windows XP version of ntdll.dll is not susceptible to the WebDAV attack vector, so the ability for an attacker to exploit the vulnerability is not present.
Currently, the WebDAV specification allows a lock to be placed on a resource that does not exist to allow for resources to be reserved before their creation.
The WebDAV property model uses a name-value pair where the property name is a valid Extensible Markup Language (XML) element and the property value is empty or a valid XML element [1, 8, 9].
When a WebDAV client requests that a resource be locked using the LOCK method, the Lock Manager creates a unique lock token that is then passed back to the user as the Lock-Token header.
WebDAV (Web-based Distributed Authoring and Versioning, also called DAV) is a set of extensions to HTTP/1.1 (HyperText Transfer Protocol, the protocol spoken by Web browsers and servers) allowing you to edit documents on a remote Web server.
WebDAV is an open standard, published by the IETF (the Internet Engineering Task Force) (RFC 2518).
WebDAV is baked right into the Windows (Web Folders) and Mac OS Xoperating systems as folders, that for all intents and purposes appear to be on your local machine, but are actually network connections to a remoteserver.
Microsoft TechNet - Boletín de Seguridad MS03-007: Técnico(Site not responding. Last check: 2007-10-21)
WebDAV, defined in RFC 2518, is a set of extensions to the Hyper Text Transfer Protocol (HTTP) that provide a standard for editing and file management between computers on the Internet.
WebDAV uses IIS to pass requests to and from Windows 2000.
Because WebDAV requests travel over the same port as HTTP (normally port 80), this in essence means that any user who could establish a connection with an affected server could attempt to exploit the vulnerability.
WebDAV ("Web-based Distributed Authoring and Versioning") is a computer-to-computer communications protocol that allows site administrators and site content editors to access and edit files on a remote Web server without first needing to download them to their local computer.
In other words, WebDAV allows your computer to access a remote Web server as though it were actually part of your local computer.
WebDAV is replacing both WebSpinner and FTP as the primary method of access for all OIT Web Hosting sites.
WebDAV functionality also is embedded in common desktop operating systems, including Windows and Mac OS X, and popular applications from Adobe, Lotus, Microsoft and others.
WebDAVversion control also makes it possible for users to know which version of a file is the most current, minimizing confusion.
WebDAV imposes a common data model that includes collections, resources, locks and properties, and defines a common syntax using HTTP messages with custom methods, headers and bodies.
The WebDAVserver you use must support exclusive write locks, which guarantee that only the lock owner (the person who opened the file for editing) can overwrite the file.
For more information about WebDAV, please visit www.webdav.org/, the site produced for the WebDAV community as a central resource for documentation, specifications, software, mailing lists, and other useful items.
WebDAV, or "Web-based Distributed Authoring and Versioning," is a set of extensions to HTTP/1.1 ("HyperText Transfer Protocol," the protocol spoken by Web browsers and servers) allowing you to edit documents on a remote Web server.
WebDAV is platform independent, both in terms of client and server.
There are still a few wobbly bits in Mac OS X'sWebDAV support (as with the rest of the OS), but these are mostly on the annoying rather than BAD side.
The stated goal of the WebDAV working group is (from the charter) to "define the HTTPextensions necessary to enable distributed web authoring tools to be broadly interoperable, while supporting user needs", and in this respect DAV is completing the original vision of the Web as a writeable, collaborative medium.
Several APIs for WebDAV have been developed, and there were no "gotchas" in their development.
WebDAV has been designed so that existing applications can easily add WebDAV support, since locks apply to entire resources, and the namespace operations support "File...
The stated goal of the WebDAV working group is (from the charter) to "define the HTTPextensions necessary to enable distributed web authoring tools to be broadly interoperable, while supporting user needs".
WebDAV serves as a network file system suitable for the Internet, one that works on entire files at a time, with good performance in high-latency environments.
I’ve recently started using WebDAV to share files with a colleague at another University, for a joint project.
So far I use webdav for managing/synching Bookmarks (OmniWeb) and iCal (not willing to shell out $100 for a.Mac account, for a feature that ought to be free), and I do not much care whether this is secure or not.
Using stunnel to forward a local port to https:// on the server is a possibility, but proxying DAV is tough (you need to patch the server since DAV by default uses absolute URLs for COPYs and MOVEs).
Other operations that are supported in the WebDav view: renaming folders and files, deleting folders and files.
WebDAV is a nifty tool that allows you to drag and drop files from the Dotlrn server to the Windows desktop on your own PC, and back again, much as you likely already do with Windows Explorer.
We're using file-storage with webdav for day to day filestorage and find ourselves not using the native Windows webfolders as they still have some issues.
WebDAV stands (loosely) for "Web-based Distributed Authoring and Versioning." DAV is an IETF Proposed Standard (RFC2518), open source, and available for development.
Until these security flaws are addressed and rectified, a WebDAV access to your UO computing account will unfortunately not be possible.
The WebDAV folder opens in IE as if it were another web page, but you can drag and drop files and folders to the WebDAV folder as though it were any other mounted directory:
WebDAV is an XML based protocol, it defines a set of new methods (PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, UNLOCK) and a set of new headers (DAV, Depth, If, Destination,...).
Download the WebDAV distribution of Jigsaw, or if you want to have fun, configure your Jigsaw by yourself.
Note about PASSWORD: The default webdav user is "jigsaw" and the default password is "jigsaw".
A WebDAV client is built into the application for connecting to remoteWebDAV shares that contain web documents, images, etc. The whole suite of WebDAV methods is provided for opening, closing, modifying, renaming and locking files.
These clients are embedded in the operating system and provide GUI access to WebDAV shares through the same file and directory interface used to display, for example, the contents of the hard drive.
HTTP commands are sent to the WebDAVserver when performing actions such as deletion, filename modification, editing, viewing properties, etc.