429 Error, RateLimit Reset in Header?

[Dusty]

Maybe I'm going crazy, but I'm pretty sure the 429 error response headers use to include X-RateLimit-api_followers-Reset, and is now missing?

I'm having trouble with 429 errors again. My app checks the API response headers for X-RateLimit-api_followers-Reset time, and if I'm out of calls sleeps until more calls are available. However, my app doesn't persist Tumblr's API rate limit state between user requests. Instead, if it's a new user request, I go ahead and call the Tumblr API, and if I get a 429 on the first call, I just wait until X-RateLimit-api_followers-Reset, but I'm no longer seeing this value in the 429 response.

Can we get the rate-limit reset time added back to the 429 error response? Or, if I'm crazy and it never existed, would it be possible to add it?

[John Bunting]

Thanks for the report. We'll check it out.

--
You received this message because you are subscribed to the Google Groups "Tumblr API Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tumblr-api+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[John Bunting]

Hey Dusty,

I'm definitely still seeing the headers and they are reporting correctly for me

x-ratelimit-api_followers-limit: "60"

x-ratelimit-api_followers-remaining: "59"

x-ratelimit-api_followers-reset: "1392992334"

On a recent call I just made. 

--
John Bunting

Simplicity is prerequisite for reliability
    --Edsger W. Dijkstra

[Dusty]

Hi John! Thanks for looking into this!

The rate-limit headers are showing up fine in the successful 200 responses, but I believe once a 429 response occurs, those headers aren't included. Where I'm expecting to see something like:

HTTP/1.1 429 Rate Limit Exceeded

x-ratelimit-api_followers-limit: "60"

x-ratelimit-api_followers-remaining: "0"

x-ratelimit-api_followers-reset: "1392992334"

This is what I'm seeing: https://snap.apigee.com/1p3ziD9

I believe that those headers use to be included in 429 responses, but I could be wrong.