Navigation Menu

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

Set OAuth::remote() to use \Request::forge() with cURL. #7

Merged
merged 1 commit into from Apr 23, 2012
Merged

Set OAuth::remote() to use \Request::forge() with cURL. #7

merged 1 commit into from Apr 23, 2012

Conversation

m4tthumphrey
Copy link
Contributor

This provides scope for better exception handling and maintainability.

This provides scope for better exception handling and maintainability.
@philsturgeon
Copy link
Contributor

I tried this before and was constantly getting 404 errors, even when a 500 or 401 was being thrown - which pissed me off. Is this no longer the case?

@m4tthumphrey
Copy link
Contributor Author

You mean you were getting them as an exception from the Request object? It could well be the case actually as I have only been catching RequestStatusException. I will investigate now.

@m4tthumphrey
Copy link
Contributor Author

Just checked with Twitter and my package (which is what prompted this pull request - https://github.com/m4tthumphrey/fuel-api/blob/master/classes/provider/oauth/twitter.php) and a faulty access token. RequestStatusException was thrown with an error code of 401. It would say that it is functioning correctly...?

philsturgeon pushed a commit that referenced this pull request Apr 23, 2012
Set OAuth::remote() to use \Request::forge() with cURL.
@philsturgeon philsturgeon merged commit 5b5b660 into fuel-packages:master Apr 23, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants