search

appdotnet / api-spec

App.net API Documentation is on the web at https://developers.app.net. Source for these docs is in the new-docs branch here. Please use the issue tracker and submit pull requests! Help us build the real-time social service where users and developers come first, not advertisers.
https://developers.app.net
950 stars 98 forks source link

X-RateLimit-* headers not being sent in API responses #313

Closed briancline closed 11 years ago

briancline commented 11 years ago

Sent out a few questions about this last night but not sure if anyone has looked into it. Looks like the documented X-RateLimit headers aren't being sent in API responses. This is occurring for both authenticated and unauthenticated requests.

The documentation mentions these headers will be present in responses:

X-RateLimit-Remaining: 4959
X-RateLimit-Limit: 5000
X-RateLimit-Reset: 3600

However, these are the only headers I'm seeing (this example was a request for /stream/0/posts/tag/rollout; I've not yet seen any other calls which include the rate limit headers):

Server: nginx/1.2.6
Content-Type: application/json
Content-Length: 2529
Connection: keep-alive
X-ADN-Migrations-Enabled: follow_pagination=1&disable_min_max_id=1&pagination_ids=1&response_envelope=1
Strict-Transport-Security: max-age=86400
Date: Wed, 13 Mar 2013 04:57:19 GMT
Access-Control-Allow-Origin: *
P3P: CP="App.net has no P3P policy."
mxml-barmstrong commented 11 years ago

You're absolutely right - we introduced a regression that caused us to not send these headers. You should be able to see them again.

briancline commented 11 years ago

Excellent, they are indeed showing up again. Thanks for looking into it!