On 3/8/06, Bob Ippolito <[EMAIL PROTECTED]> wrote: > The right fix for #430 would've been to ensure unicode strings from > browser input, instead of ensuring potential garbage makes its way > into the JSON output. In this case, it would be a change to the way > URLs (at least the query string) are handled. > > This could be fixed by making cherrypy.lib.parseQueryString look at > the resultant dict for keys that are outside of ASCII and decoding > them to UTF-8... or it could be done as a filter like the formencode > NestedVariablesFilter in startup.
You're correct about the diagnosis and the solution. Thanks for looking at this! I've reopened #430 and rolled back the original patch. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
