WebDAV is a protocol extension to HTTP 1.1 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. mod_dav is an implementation of the WebDAV specification.
The term OraDAV refers to the capabilities available through the mod_oradav module. mod_oradav is the Oracle module that is an extended implementation of mod_dav, and is
integrated with the Oracle HTTP Server. mod_oradav can read and write not only to local files, but
also to an Oracle Database. The Oracle Database must have an OraDAV driver installed.
Similar to the portal DAD configuration file, WebDAV has it own configuration file (ORACLE_HOME/Apache/oradav/conf/oradav.conf) that contains the OraDAV parameters
and start with DAV and DAVParam. These parameters are specified within a "Location"
directive. The oradav.conf file is included in the httpd.conf file in an include statement.
By default, the OracleAS Portal DAV URL is:
http://hostname:portno/dav_portal/portal/
For example:
http://mysite.oracle.com:7777/dav_portal/portal
The dav_portal part of the URL is the default name of a virtual directory used to differentiate between portal access through a WebDAV client and portal access that uses the pls virtual directory. portal is the DAD of the portal installation.
Due to the way some WebDAV clients behave, users might experience authentication requests multiple times. To avoid this, the portal administrator can enable the cookie option by adding the following line to the oradav.conf file:
DAVParam ORACookieMaxAge '<'seconds'>'
where seconds is the amount of time in seconds before the cookie expires.
For example a value of 28800 is 8 hours and means that once a user has logged on through a
WebDAV client, he or she will not be prompted for a user name and password again until 8 hours has passed.
No comments:
Post a Comment