Add option to store oauth parameters in Header or Body of request #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After moving my WP website to another ISP, I could not authenticate my desktop app anymore. The method getRequestToken() raised the following error: "No OAuth parameters supplied".
After extensive research I found out that Apache does not pass the Authorization header by default to fgci. See Add Authorization header to WordPress .htaccess rules #161. Unfortunately the suggested solution to change .htaccess did not work in my case.
Since WP-API/OAuth1 accepts parameters in Header, Post and querystring (See docs) , I've added an option to tell your request() method to add the OAuth1 parameters to the Body instead of the Header.
Not sure if my proposed change is the best solution but it works for me...