-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
X-Page-Usage in response header #127
Comments
Not yet, but I'd be happy to merge a pull requests that does that! |
In my own testing, I've not seen this header, |
I looked for the Example headers from FB after sending a message successfully to Facebook's API: {
"access-control-allow-origin"=>["*"],
"pragma"=>["no-cache"],
"cache-control"=>["private, no-cache, no-store, must-revalidate"],
"facebook-api-version"=>["v2.11"],
"expires"=>["Sat, 01 Jan 2000 00:00:00 GMT"],
"x-fb-rev"=>["3659829"],
"content-type"=>["text/javascript; charset=UTF-8"],
"x-fb-trace-id"=>["snipped"],
"strict-transport-security"=>["max-age=15552000; preload"],
"x-fb-debug"=>["snipped characters"],
"date"=>["Tue, 20 Feb 2018 14:40:50 GMT"],
"connection"=>["close"],
"content-length"=>["85"]
} |
Reading the FB docs, I now see why I'm not seeing that header yet:
So if you are approaching that rate limit, THEN Facebook includes that header in the response. Rate limits are divided between app and Facebook pages:
|
Alright, cool, that makes sense! |
Hi
As per the Facebook Messenger documentation (https://developers.facebook.com/blog/post/2016/06/16/page-level-rate-limits/), the response header contains additional information:
Is there any way of accessing these header values using this gem?
Thanks,
Sridhar
The text was updated successfully, but these errors were encountered: