WebDAV Security Considerations Globalization Support Considerations with OraDAV

Configuring mod_oradav 9-13 the file system provides for conversion of all possible characters in client requests. The default is Off. For access to the local file system, the character set for the file system must be the same as, or compatible with, the character set for URLs embedded in client requests. The character set for the file system must provide for conversion of all possible characters in client requests. The NLS_LANG parameter value must represent the character set of both the client and the OraDAV server. You must also specify a value of On for the parameter DAVOraUseNLSLang. For example, assume that you are using Web folders on a system where the files have ShiftJIS characters and that the file system under dav_public is represented by the operating system in the JAPANESE_JAPAN.JA16SJIS character sets shown in Figure 9–2 . Figure 9–2 OraDAV Access to File System with ShiftJIS Characters You must do the following:

1. Set the NLS_LANG value to JAPANESE_JAPAN.JA16SJIS.

2. Include the following in the mod_oradav.conf file:

Location dav_public DAV On DAVOraUseNLSLang On Location Note: If you use Microsoft Internet Explorer with OraDAV and a multibyte character set, you must disable the Internet option Always send URLs as UTF-8, located under the Advanced tab in the Internet Options section. By default, this option is enabled. The requirement to disable this option applies to both database access and file system access. 9-14 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server

9.6 Location of DAV Files

When the ORACLE_HOMEohscastemplatesdefaultmoduleconfmod_ oradav.conf file is configured to use file storage, it places the files by default in: ORACLE_INSTANCEconfigOHSohs_namemoduleconf Oracle Fusion Middleware Backup and Recovery Service backs up this default location. If you change the location where the files are stored, and you want Oracle Fusion Middleware Backup and Recovery Service to backup the files, then you must register the new location. Part III Part III Appendixes and Glossary This part contains the following appendixes and a glossary: ■ Appendix A, Using Oracle Plug-Ins for Third-Party Web Servers ■ Appendix B, Frequently Asked Questions ■ Appendix C, Troubleshooting Oracle HTTP Server ■ Glossary A Using Oracle Plug-Ins for Third-Party Web Servers A-1 A Using Oracle Plug-Ins for Third-Party Web Servers This appendix explains how the Oracle Proxy Plug-In and Oracle SSO Plug-In enable you to use Oracle Fusion Middleware components in conjunction with a third-party HTTP listener. This appendix includes the following sections: ■ Section A.1, Using Oracle Proxy Plug-In ■ Section A.2, Using Oracle SSO Plug-In Documentation from the Apache Software Foundation is referenced when applicable. A.1 Using Oracle Proxy Plug-In Oracle Proxy Plug-In enables you to proxysend requests from a third-party HTTP listener to Oracle Fusion Middleware. The Oracle Proxy Plug-In is provided and certified to work with Sun Java System Web Server Enterprise Edition on UNIX and Microsoft Windows systems, or Microsoft Internet Information Server IIS v6.0 and 7.0. For other third-party HTTP listeners, you can use the respective listeners native proxy functionality. This section includes the following topics: 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 in Stand-Alone Mode” in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier. See Also: http:www.oracle.comtechnologysoftwareproductsi asfilesfusion_certification.html for complete certification information.