Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Visiting the page: yields the following headers:

enter image description here

Notably absent are the X-RateLimit-Max and X-RateLimit-Current headers that show up in API queries to the sites themselves.

share|improve this question
up vote 1 down vote accepted

For the time being, as everything on Stack Auth is "query when needed (which is rarely), cache for a day", the inclusion of rate limit headers is kind of pointless.

Basically, if you ever need to check that you aren't hitting your quota... you're probably doing something wrong. There are naturally exceptions, but still in 99% of all cases the headers are pointless.

If Stack Auth ever grows methods that merit more aggressive calling, it'll gain some indication of rate limiting.

share|improve this answer
Well, one of my example scripts is designed to pull the rate limit from the last request's headers. When that happens to be a request with StackAuth, I am without that information... which is unfortunate. – Nathan Osman Feb 13 '11 at 3:12
@George - The StackAuth 1.0 methods behave(d) the same way, its not a 1.1 change. – Kevin Montrose Feb 13 '11 at 3:19

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .