Skip to content
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

Enforce signed header #35

Closed
maidmaid opened this issue Feb 22, 2015 · 1 comment
Closed

Enforce signed header #35

maidmaid opened this issue Feb 22, 2015 · 1 comment

Comments

@maidmaid
Copy link

Using signed headers, we can call more times certains POST endpoints. For example, POST /users/user-id/relationships endpoint without signing the limit is 20 calls per hour, with signature, we can do 60 (https://instagram.com/developer/limits/). To sign the header, here is the doc: https://instagram.com/developer/restrict-api-requests/#enforce-signed-header.

My implementation proposal:

  • Add a boolean parameter enforce_signed_header, false by default.
  • Add a ips parameter, 127.0.0.1 by default.
  • If enforce_signed_header is true, we add a header Insta-X-Forwarded-For to request Guzzle having as value <ip_information>|<signature> as described in the documentation page.
@sesser
Copy link
Owner

sesser commented Mar 9, 2015

@sesser sesser closed this as completed Mar 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants