William A. Rowe, Jr. wrote:
For what it's worth I also did try using the ldap_search_ext_sW call
directy inside the uldap_cache_checkuserid function but that resulted
in a filter error.
Yup :)
So if you were to tweak things to decode utf-8 into unicode and then
invoke
the W flavor, it should work. But I don't think we actually wrap
ldap_search_ext_s in apr-ldap, do we? Meaning that will be a heck of a
messy macro override.
Bill,
the case where we're seeing this none of the arguments contain anything
other than US ASCII characters. If you're ldap_search_ext_sW call
contains only US-ASCII but the returned DN contains UTF-8 shouldn't this
still work or is there something I'm missing here?
Thanks,
Andy
