Using Apache to Authenticate Users Using mod_osso to Authenticate Users

9 Configuring mod_oradav 9-1 9 Configuring mod_oradav This chapter describes distributed authoring and versioning DAV concepts, and explains how to configure OraDAV using the mod_oradav module. The mod_oradav module enables you to use OraDAV to access content in files from a Web browser or a WebDAV client. This chapter includes the following sections: ■ Section 9.1, Introduction to the mod_oradav Module ■ Section 9.2, Configuring mod_oradav ■ Section 9.3, WebDAV Security Considerations ■ Section 9.4, OraDAV Performance Considerations ■ Section 9.5, Globalization Support Considerations with OraDAV ■ Section 9.6, Location of DAV Files

9.1 Introduction to the mod_oradav Module

The mod_oradav module is an extended implementation of the Apache implementation of the WebDAV specification. The mod_oradav module is an OCI application written in C and is integrated with Oracle HTTP Server. The mod_oradav module enables WebDAV clients to connect to files, read and write content, and query and lock documents. This section includes the following subsections: ■ Section 9.1.1, WebDAV ■ Section 9.1.2, OraDAV ■ Section 9.1.3, OraDAV Architecture Note: The information in this document is applicable when Oracle HTTP Server is installed with Oracle WebLogic Server and Oracle Fusion Middleware Control. It is assumed that readers are familiar with the key concepts of Oracle Fusion Middleware, as described in the Oracle Fusion Middleware Concepts Guide and the Oracle Fusion Middleware Administrators Guide. For information about installing Oracle HTTP Server in standalone mode, see “Installing Oracle Web Tier Without Oracle WebLogic Server” in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier. 9-2 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server ■ Section 9.1.4, OraDAV Usage Model ■ Section 9.1.5, PROPFIND Security

9.1.1 WebDAV

WebDAV is a protocol extension to HTTP that supports distributed authoring and versioning. With WebDAV, the Internet becomes a transparent read and write medium, where content can be checked out, edited, and checked in to a URL address. WebDAV enables collaboration among authors building Web sites. WebDAV also serves as universal read and write access protocol to arbitrary hierarchies of content, not necessarily Web sites. With WebDAV, you can save content to a URL provided by an Internet Service Provider ISP, and then access and optionally change that content from various devices.

9.1.2 OraDAV

OraDAV refers to the set of capabilities available through the mod_oradav module to Oracle Fusion Middleware users. Some OraDAV-specific terms include: ■ OraDAV: Code in the Oracle HTTP Server that supports file-based DAV access. Apache DAV directives can be used with OraDAV. ■ OraDAV API: Stored procedure calls that are used by the OraDAV driver to provide support for the following WebDAV functions over the Internet: ■ Reading and writing documents ■ Locking and unlocking documents ■ Managing, such as creating, populating, and deleting, hierarchies of information ■ Retrieving properties associated with documents ■ Associating properties with specific documents ■ OraDAV driver: Stored procedure implementation of the OraDAV driver API that runs in Oracle and manages a repository. The primary users of OraDAV are Oracle HTTP Server Web administrators and content editors. End users interact only indirectly with OraDAV through Web Note: When a WebDAV client first connects to Oracle HTTP Server, it must use the full ServerName string in the URL for the connection. Do not use an abbreviated form of the server name. For example, if the server name value is server1.example.com, then connect to Oracle HTTP Server using the string http:server1.example.com:7778, not an abbreviated form such as http:server1:7778. If you use an abbreviated form, the connection might succeed, but COPY and MOVE operations will fail to run, and generate BAD_ GATEWAY errors. See Also: For more information about DAV directives, see the article written by Greg Stein gsteinlyra.org available at http:www.webdav.orgmod_davinstall.htmlapache Configuring mod_oradav 9-3 browsers or WebDAV client tools. OraDAV interaction requires the following proficiency: ■ The Web administrator needs to know how to start and stop Oracle HTTP Server, and how to configure Oracle HTTP Server to direct URL traffic to an OraDAV driver. ■ The content editors need to know how to connect to the server, and upload and retrieve files.

9.1.3 OraDAV Architecture

The mod_oradav module, which includes OraDAV, is part of the Oracle HTTP Server architecture. A simple form of the architecture is illustrated in Figure 9–1 . Figure 9–1 OraDAV Architecture Figure 9–1 shows a WebDAV client, such as Web folders, passing HTTP requests to Oracle HTTP Server. If the request is for content stored in the file system, the mod_ oradav module handles the access. If the request is for content stored in Oracle Portal, the OraDAV API handles the access. The OraDAV API capabilities are equivalent to using the mod_oradav module running with a file system. The following HTTP methods are supported by the OraDAV API: ■ COPY: Copies files within a Web site folder. ■ DELETE: Deletes files within a Web site folder. ■ MOVE: Moves files within a Web site folder. ■ MKCOL: Makes a new directory. ■ GET: Retrieves a file from the server. This method is not supported by Oracle Web Cache. ■ PUT: Puts a file back to the server. This method is not supported by Oracle Web Cache.