fetch: fix small spec inconsistency #1158
Merged
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 condition is not yet possible to meet so I couldn't add a test
(sorry!).
response
is always nullundici/lib/fetch/index.js
Line 475 in 09059fb
undici/lib/fetch/index.js
Line 529 in 09059fb
responseTainting
to eitheropaque
orcors
.response.status === 0
would be a network error)undici/lib/fetch/index.js
Line 605 in 09059fb
The spec says that "[a] basic filtered response is a filtered response
whose type is "basic" and header list excludes any headers in internal
response’s header list whose name is a forbidden response-header name."
The library was incorrectly excluding valid headers.
If
data:
,blob:
,about:
, orfile:
URIs are ever supported, thischange will be needed.