fix: handle fetch headers that are Headers objects #6320
Merged
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
jcesarmobile
requested review from
ItsChaceD,
giralte-ionic,
IT-MikeS and
theproducer
giralte-ionic
approved these changes
Feb 22, 2023
giralte-ionic
approved these changes
Feb 22, 2023
IT-MikeS
approved these changes
Feb 22, 2023
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.
If the fetch call uses headers created with the Headers interface, they can't be handled by http plugin since they are not serializable on iOS and are serializable on Android but are not proper headers.
This PR checks if the headers are a instance of
Headersand use its entries to get the headers javascript object.