> ----- Forwarded message from Robert Scheck <[EMAIL PROTECTED]> ----- > when RPM 4.4.7 (devel) got IDN support (umlaut domains), I recognized that > neon currently has no IDN support and wrote a small patch attached to this > e-mail. I don't know whether it is sane enough, but it just works here for > about two months now.
Hi Robert, thanks for sending in the patch. I spent some time looking at this a while back and came to the conclusion that it's not actually correct to have IDN support in neon at all. IDNA needs to be done at application level - hence the "A". At HTTP protocol level, only the ACE (converted-to-ASCII form) can ever be used; that means in Host headers, in Location headers, in PROPFIND response bodies, and so on. So, when using neon, the app should only ever be passing an ASCII domain name to ne_session_create; to add IDNA support, the app needs to be using libidn (or equivalent) directly, and doing the conversion itself. Regards, joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
