James Gardner wrote: > > <yoink> Is it considered standard practice to allow > non-ascii usernames though? Particularly since usernames are supposed to > be case-insensitive in AuthKit?
I'd like to make allowing non-ascii usernames standard practice, trying to make pylons i18n the best possible. According to `recent activity from the IETF`_, it is still not practical to support anything other than iso-8859-1 in for Basic or Digest auth, but for forms and any other non-HTTP authentication method it is doable now. .. `recent activity form the IETF`: http://lists.osafoundation.org/pipermail/ietf-http-auth/2006-September/000390.html Regarding case-insensitive usernames in AuthKit, I'm assuming you're only referring to not-usable-for-production example of using usernames and passwords directly in the AuthKit configuration with no backend? Cheers, David > > Cheers, > > James > > > Christoph Haas wrote: >> Hi, list... >> >> I'm using AuthKit in my application and seem to have trouble when the >> login form gets me the username as a Unicode string. I use the famous >> line: >> >> form_username = request.params.get('username') >> request.environ['paste.auth_tkt.set_user'](form_username) >> >> This leads to Unicode errors (I currently cannot reproduce it). Things >> start to work though when I run str() on the Unicode string before: >> >> form_username = str(request.params.get('username')) >> request.environ['paste.auth_tkt.set_user'](form_username) >> >> Does AuthKit have trouble with Unicode strings in general? Or am I >> missing a configuration option? >> >> Kindly >> Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
