403 (quota) error but way under quota - problem continues

[Jim]

It's happened again tonight. I'm using urlfetch. What I've been
told by a Google engineer is that at some point GAE sees urlfetch
looking for /etc/resolv.conf too many times and locks out my app as
dangerous.

I'm not aware of any way that I or anybody else can resolve this
because urllib and urllib2 are going to use urlfetch, too.

My code is absolutely not trying to access /etc/resolv.conf on its
own. This is something internal to Google - it doesn't show up in
the SDK at all.

The affected app is linkscocom.appspot.com running as www.linksco.com

Somebody at Google needs to fix the code. What can I do to help make
this happen?

[Nick Johnson (Google)]

Hi Jim,

I'm seeing what I can do about providing a short-term fix on our end to alleviate the problem you're experiencing, while we work on a long-term fix to eliminate the root cause.

One of our engineers has offered to take a look at your app in particular, but they'd need the full source to your app, not just the part you suspect is causing it. If this is okay with you, please contact me privately and we'll sort it out offline.

Incidentally, are you seeing a high rate of 500s? Any request that triggers this issue should result in an error. Seeing what requests cause the error might also be instructive in hunting down the root cause.

-Nick Johnson