On Fri, Mar 06, 2009 at 03:17:55PM -0800, Philip Jenvey wrote: > On Mar 6, 2009, at 2:34 PM, Ross Vandegrift wrote: > > I've got: > > config['pylons.request_options']['charset'] = None > > config['pylons.response_options']['charset'] = 'iso-8859-1' > > in my config/environment.py. > > This should work: > > config['pylons.request_options']['charset'] = None
Right, it should work. But it doesn't :) It worked fine on 0.9.6, it's just since my upgrade to 0.9.7 that its stopped doing the trick. > You can check request.charset later for what this is actually set to. > Only the value of None should disable unicode (US-ASCII won't). Okay - I tried US-ASCII just for kicks, but None is what I'm using. Any chance that specifying the response_options is confusing something? Another thing is that the method of deployment seems to affect this bug. When I'm developing with paster, all kinds of things crap out because of Unicode data being passed up the stack. In my live deployment (which uses Apache and FastCGI) this doesn't seem to be a problem. Is is possible that paster is doing something terrible in my development environment (like coercing my requests into a different character set)? Maybe I'll get a staging version of the Apache/FCGI set up so I can see what request.charset looks like in that setup. Ross -- Ross Vandegrift [email protected] "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
