Return response headers with fetch() #35
Open
Conversation
This file contains hidden or 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
If params are passed as JSON (instead of array), check and see if the access token is part of the JSON. If it is, do not throw the "You need to give parameters as array if you want to give the token within the URI" exception.
|
Good idea, unreliable solution. It should probably use And yeah, that code was never merged unfortunately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is different than issue #30 in that the http_parse_headers function here is a better implementation of parsing the headers - it accounts for a number of things that could be different about the headers.
Issue #30 also doesn't appear to have been merged, unless I am looking at it wrong.