Potential Changes to HTTP Response Codes

[John Bunting]

Hey All,

Just wanted to drop a note to the list to see if it would adversely affect anyone if we change our rate limiting response code from 503 to 429. Obviously, the 503 is incorrect and we'd like to correct it to fall more in line with standards.

Please let me know!

-- 

John Bunting

Simplicity is a prerequisite for reliability

   --Edsger W. Dijkstra

[hostj2me]

Hello,

Although a change in the error code would not affect our application, is there a place where I can read more about rate limiting and its criteria?

Thanks.

[Felix Bonkoski]

Although a change in the error code would not affect our application, is there a place where I can read more about rate limiting and its criteria?

I'd second knowing a bit more about the rate limiting. What is it targeting?  IP, Consumer Key, User Access Key?

In my case, 98% of my use of the API is with centralized data servers, not via distributed consumer applications, so how Tumblr rate limits requests is of interest / concern to me.

I don't believe I've run into the 503 "rate limit" response in the past, but my code tends to treat any 500-type errors in the same way without differentiation, so it's hard to say with certainty.

Felix