fix: Let Edge to send fetch requests using default config #1236
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.
Fixes #1233
We add
referrerbecause this comment #1177 (comment)However, there's no easy way to test this behavior, as:
fetchwon't call it's native implementation, therefore not throw an errorfetchwon't modify response object, and without it, we'll always jump intoonErrorhandler because we get nookin resp dataI'm not really convinced if this is a good idea... It just feels odd, but I cannot think of any simple, yet an acceptable solution to this issue.
Thoughts?