This patch eliminates the hardcoded charset table. Instead it
reads the charset table from a conf file. The directive
AuthLDAPCharsetConfig allows the admin to specify the charset conf
file. Is there also a need to specify additional conversions
directly in the httpd.conf
The charset conversion that is happening in LDAP is actually quite
specialized. The general functionality of converting from one charset
to another already exists in APR in the form of apr_xlat_xxx(). LDAP is
only interested in converting the user ID from a given charset to UTF-8.
Up
Brad Nicholes [EMAIL PROTECTED] wrote in news:sdf8b26d.020@prv-
mail25.provo.novell.com:
In order to solve WebDAV's problem, the
scope of this discussion needs to be much broader. Any ideas??
Hm, not really. :/
This should be done by someone with more experience to the code.
Kess
The mod_dav documentation mentions a tool lockview to be found at
modules/dav/util. But I can't found it, neither in the release not at
the CVS. Does it exist, but has never been committed? Or has it never
been written?
I've just compiled the dav mopdule for Apache 1.3 and there is the
The mod_dav documentation mentions a tool lockview to be found at
modules/dav/util. But I can't found it, neither in the release not at the
CVS. Does it exist, but has never been committed? Or has it never been
written?
Kess
