Simon Willison wrote: > We shouldn't be decoding QUERY_STRING in request.META at all - we > should leave it as urlencoded ASCII. request.META is meant to give > you access to the 'raw data' from the browser. > > We do however need to take charset stuff in to account when creating > the request.GET and request.POST arrays - that's where the query > string should be parsed and unencoded and turned in to a set of name/ > value unicode strings.
Yes, this is what I mean. Sorry for not clarifying that it's not about META. I just used QUERY_STRING as a source for GET data. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
