I managed to fix it. The problem was indeed in the displayed warning (Stripped prohibited headers from URLFetch request: ['Content-Length', 'Host']). I opened the file google/appengine/api/urlfetch_stub.py and I removed content-length and host from _UNTRUSTED_REQUEST_HEADERS. Surprisingly, it worked! I can now login again and also gdata seems to be fixed. But since hacking into Google SDK isn't the best way to solve problems, I would be still interested in what was really behind this weird behavior. It's just a bug?
On 16 bře, 12:05, tobik <[email protected]> wrote: > I'm using OpenID to authenticate users from Google Apps. I'm writing > the app in django and the authentication process uses libraries > django_openid_auth and openid. It worked like a charm until yesterday > when I tried to login and I got this message: > > OpenID authentication failed: Server denied check_authentication > > Funny is that when I deploy the application to the server, it does > work! The same code fails on local dev server but works online! And I > have no idea what has changed on my pc. I have recently updated my > Linux box but how could that affect such thing like OpenID > authentication process? Maybe some Python update? I tried to update > the SDK but it didn't help. > > I also checked the log and I found this warning: > > WARNING 2011-03-16 10:51:21,933 urlfetch_stub.py:325] Stripped > prohibited headers from URLFetch request: ['Content-Length', 'Host'] > > This might have been there before but I didn't noticed it. And also > this warning appears only on dev server, it's not there when I checked > the log in appengine control panel. So it might be it however I have > no idea how to fix it. > > And another problem appeared as well. The script which fetches users > from Google Apps Domain (using gdata) also stopped working, it prints > following message: > > sequence item 0: expected string, int found > > However again, it DOES work online, with no change in code. I found > that I should use "gdata.alt.appengine.run_on_appengine(service)" but > it doesn't fix the problem on localhost and breaks it on real server > so I guess it shouldn't be there. And mentioned warning appears here > as well. > > I think these two problems might be related so I'm posting them > together. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
