On Wed, Apr 30, 2008 at 10:12 AM, chatchai <[EMAIL PROTECTED]> wrote:
> > Hi, > With Django trunk version, when make a web request with following URL, > Django return 400 client error, > > - http://localhost/%A1 (- http://localhost/? <http://localhost/%E0%B8%81>) > See the discussion (particularly hte 2nd-to-last comment) in: http://code.djangoproject.com/ticket/5738 Django assumes URIs are utf8 encoded. If a URI comes in that has invalid utf8 data, Django generates a 400 error. Per the comment, the fix for 5738 allows for overriding this behavior, but it sounds like it is intended only for cases where you've got to deal with legacy systems that put non-utf8 data into their URIs, before utf8 was codified as the standard. So, unless you are dealing with a case like that, the best path would be to avoid using non-utf8 encodings in your URLs. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
