Folders and WebDAV Administration Guide PDF
About WebDAV > WebDAV Architecture


WebDAV Architecture

WebDAV support is implemented in the content server through a custom component, which handles WebDAV requests directly. A WebDAV request to the content server follows the following process (as illustrated in the figure below):

  1. The WebDAV client makes a request to the content server.
  2. The message is processed by the web server through a custom filter.
  3. On the content server, the WebDAV component performs the following functions:
    • It recognizes the client request as WebDAV.
    • It maps the client request to the appropriate WebDAV service call on the content server.
    • It converts the client request from a WebDAV request to the appropriate content server request.
    • It connects to the core content server and executes the content server request.
  4. The WebDAV component converts the content server response into a WebDAV response and returns it to the WebDAV client.
Important: WebDAV uses several non-standard HTTP methods, including PROPFIND, PROPPATCH, MKCOL, DELETE, COPY, MOVE, LOCK, and UNLOCK. Many third-party applications   such as firewalls, proxy servers, load balancers, and single sign-on applications   do not allow these methods by default. If your network includes any of these applications, you might need to reconfigure them to allow the WebDAV methods.

Copyright © 1996, 2007, Oracle. All rights reserved.