Has there been any update to this issue in the last six months?
Is there any tracking for this issue, or is this the best place to look for updates?
I experiencing a similar problem; should I try upgrading to the paid account as a test?
For the record, I get a 403 error when my browser tries to hit this URL: http://rangevsrange.pythonanywhere.com/login/?next=http://rangevsrange.pythonanywhere.com/home&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.response_nonce=2014-02-23T01%3A15%3A14Z9enAbocgbLt9LA&openid.return_to=http%3A%2F%2Frangevsrange.pythonanywhere.com%2Flogin%2F%3Fnext%3Dhttp%3A%2F%2Frangevsrange.pythonanywhere.com%2Fhome&openid.assoc_handle=1.AMlYA9VPNuSu_D8uGznXovWmossfSNUf-wfdNFN9N0jcLKvYk1SmQxAqwUVpQ3DM&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname%2Cext1.value.lastname%2Cext1.type.language%2Cext1.value.language%2Cext1.type.email%2Cext1.value.email&openid.sig=Nu%2BEcbJbfo11eMerb2iRQJ6%2B2O0%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawnsk0QDCwo7kRa2tfXIakI19w_pZESHNgA&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawnsk0QDCwo7kRa2tfXIakI19w_pZESHNgA&openid.ns.ext1=http%3A%2F%2Fopenid.net%2Fsrv%2Fax%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http%3A%2F%2Faxschema.org%2FnamePerson%2Ffirst&openid.ext1.value.firstname=Guy&openid.ext1.type.lastname=http%3A%2F%2Faxschema.org%2FnamePerson%2Flast&openid.ext1.value.lastname=Upstairs&openid.ext1.type.language=http%3A%2F%2Faxschema.org%2Fpref%2Flanguage&openid.ext1.value.language=en&openid.ext1.type.email=http%3A%2F%2Faxschema.org%2Fcontact%2Femail&openid.ext1.value.email=rangevsrange%40gmail.com#
All I see on the error log is: 2014-02-23 01:15:08,843 :Starting new HTTPS connection (1): www.google.com
Access log shows my request and that the response is a 403. Server log also shows that www.google.com is being hit (or at least attempted, I guess).