|Issue 961:||When the app is over quota, respond with 503 Service Unavailable instead of 403 Forbidden|
|29 people starred this issue and may be notified of changes.||Back to list|
The documentation states that “for resources that are required to initiate a request, when the resource is depleted, App Engine returns an HTTP 403 Forbidden status code for the request.” (https://code.google.com/appengine/docs/quotas.html#When_a_Resource_is_Depleted) Wouldn't it be more appropriate to return a 503 Service Unavailable error in that case to notify search engine bots and other automatic clients that this is a temporary condition due to server overloading? I'm worried that a 403 Forbidden error might suggest to some bots that the pages are gone more or less permanently. At least that’s what a 403 often means in practice, so even though it's not in the spec, some bots might decide to treat the forbidden pages as dead. That would be unfortunate. Anyway, compare the following paragraphs from the HTTP 1.1 specification: http://tools.ietf.org/html/rfc2616#section-10.5.4 http://tools.ietf.org/html/rfc2616#section-10.4.4
Dec 28, 2008
And a 503 response can include a Retry-After header specifying the date and time when the quota is going to be replenished.
Jan 12, 2009
(No comment was entered for this change.)
Labels: -Type-Defect Type-Feature
Jan 25, 2009
It would be better if a custom error page could be displayed
Jan 25, 2009
I totally agree. See issue 67 .
Oct 14, 2009
We expect to change this from a 403 to a 503 at some point in the future.
Dec 8, 2009
This issue was fixed in App Engine 1.2.8
Feb 15, 2010
Please update the docs. They still mention the 403 Forbidden status code. https://code.google.com/appengine/docs/quotas.html#When_a_Resource_is_Depleted
Feb 17, 2010
Filed issue 2792 about updating the docs.
Oct 21, 2012
App engine is returning Error 500 for OverQuotaError.It is clearly mentioned in the App engine Log. http://dl.dropbox.com/u/7384181/OverQuota.png . As per the above comment it should be 503. Does anyone have better answer for this http://stackoverflow.com/questions/12969438/custom-error-page-for-over-quota-error-in-webapp2
|► Sign in to add a comment|