Wesley,
Sure there are robot clicks. The IP addresses you mentioned are indeed
bots.
However, there were quite many real human clicks that caused the problem.
For instance, in the app id 'sa-beta' error log, there is the following
entry:
03-15 03:07PM 52.148 /channel/ 500 949ms 330cpu_ms 9kb Mozi
i see several of these errors. if get_current_user() returns None, it
really does mean that whoever/whatever access that page isn't logged
in. perhaps it's a TaskQueue task or some robot hitting your page.
do you recognize the IP addresses in your log entries? for example,
one of them is 66.249.65
Wesley,
The problem still exists, although it doesn't seem causing real harm. You
can take a look at app id 'sa-beta'.
Login is required on that page in my app. The following is our code that
logs the error entry. The page was displayed correctly when the error was
logged.
*user = users.get_
hi alan,
can you let us know if you're still seeing this problem? have you seen
this yourself or was this reported by your users? if the latter, can
you be sure that they have signed in? (does your app require login
before users can access the rest of your app?)
if it's still happening, pls send
We have noticed this happening for a few app IDs we have since yesterday. It
is getting less frequent for now, but still happening. Wondering if the GAE
team is aware of this.
--
http://twitter.com/alanxing
http://twitter.com/xinghailiang
http://facebook.com/alanxing
http://www.linkedin.com/in/al
