I'm not sure what has changed, but I just fixed my issue by using
msg.encode("utf8") before passing msg to hmacSha1. It was working
without this step in the past.
Alex
On Mon, Oct 6, 2008 at 5:41 AM, Sylvain <[EMAIL PROTECTED]> wrote:
>
> I've seen many issues with charset (Unicode) like this one :
> http://code.google.com/p/googleappengine/issues/detail?id=573
>
> Could you explain more your issue/code that seems broken.
>
> These issues are very annoying.
>
> Regards
>
>
> On 6 oct, 08:50, Alex Epshteyn <[EMAIL PROTECTED]> wrote:
>> I had an issue with European characters in my application that I fixed
>> two months ago. However, the issue has recently returned.
>>
>> I started seeing "UnicodeEncodeError: 'ascii' codec can't encode
>> character u'\xe3' in position 180: ordinal not in range(128)" in the
>> production logs about a week ago and after I upgraded the dev app
>> server, I started seeing it locally as well. The release notes for
>> 1.1.5 say "Set the webapp Request charset property more accurately
>> from CONTENT_TYPE." This must have been done to match some change in
>> production.
>>
>> My question is - what has changed in production regarding request
>> charset handling since August?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
