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

x-ratelimit bug? #19

Closed
abraham opened this issue Feb 26, 2010 · 5 comments
Closed

x-ratelimit bug? #19

abraham opened this issue Feb 26, 2010 · 5 comments
Labels

Comments

@abraham
Copy link
Owner

abraham commented Feb 26, 2010

https://mail.google.com/mail/#inbox/12705a13fbc6754a

@navarr
Copy link

navarr commented Feb 26, 2010

Does this have anything to do with the code I contributed? :o

@abraham
Copy link
Owner Author

abraham commented Feb 26, 2010

Tangentially. Got an email about a possible mis-naming of a variable. I feel like it worked properly for the last release but I want to do some live testing to verify.

I tried to get the x-ratelimit info via "$this->http_info", without success.

http://github.com/abraham/twitteroauth/commit/441e1fb5549e80c40d8f12838357994060550f45
http info is now saved at $this->http_info including x-ratelimit info

Line 209 in twitteroauth/twitteroauth.php:
$this->http_info = array_merge($this->http_info, curl_getinfo($ci));

Maybe it should be like this?
$this->http_info = array_merge($this->http_header, curl_getinfo($ci));

@iamdamnsam
Copy link

What is the call to get the x-ratelimit or any other header info?

@iamdamnsam
Copy link

NM, abraham let me know in another post, $connection->http_info

@iamdamnsam
Copy link

Actually for the x-header stuff it is $connection->http_header

@abraham abraham closed this as completed Jan 7, 2015
Repository owner locked and limited conversation to collaborators Dec 30, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants