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
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 until
You are absolutely right, there are other modules that need to do header
conversion. In a previous email, Bill Rowe pointed out that WebDAV also suffers from
charset mismatch, but in a different way than auth_ldap. WebDAV needs the URI
converted as well as other header entries in order to
You are absolutely right, there are other modules that need to do
header conversion. In a previous email, Bill Rowe pointed out that
WebDAV also suffers from charset mismatch, but in a different way than
auth_ldap. WebDAV needs the URI converted as well as other header
entries in order to
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 file through a
