About the mod_encoding module

The open source mod_encoding module adds WebDAV support for non-ASCII filenames. To support non-ASCII filenames, you must enable mod_encoding and dav_module.

By default, mod_encoding is disabled. The module is installed and configuration directives are present in the Apache config file. These aren’t activated because the LoadModule and AddModule directives that inform Apache about mod_encoding are disabled.

The Apache configuration file contains a specific set of configuration directives that should be sufficient for most needs. To modify directives you must use a text editor and edit the file /Library/Server/web/config/apache2/httpd_server_app.conf.

mod_encoding supports the following server configuration directives:

This directive enables and disables mod_encoding. Correct operation of mod_encoding also requires that the special version of mod_dav, mod_ dav_encoding, be enabled as well.

Although WebDAV clients are expected to send data in UTF-8 or any other properly detectable style, some clients send data in non-autodetectable platform-local encoding, thus requiring this directive, which maps encoding names to client types.

This directive specifies encodings expected from each client type. The clients are identified by agent name. The agent name can be specified as a pattern using extended regexp. Never use “.*” for the agent name. Instead, use DefaultClientEncoding.

This module uses CoreFoundation’s CFString and supports all encoding supported by it. In general, IANA-registered encoding names are supported.

This directive tells the default set of encodings what to expect from various clients. You don’t need to specify UTF-8 because it’s the default.

This directive supports the behavior of Windows XP when accessing a password-protected resource. Windows XP clients prepend “hostname\” to the real user name. Enabling this option strips off the “hostname\” part, so only the “real” user name is passed to the authentication module.