You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This header initializer option is supported by the Headers constructor parameter, which can be
a simple object literal with String values, an array of name-value pairs, where each pair is a 2-element string array; or an existing Headers object.
Testing in Chrome 109.0.5414.87, I found an inconsistency between what is supported by whatwg-fetch and what is supported by Chrome's native Fetch API.
Chrome Fetch:
Object
Array
Chrome Fetch Headers class
whatwg-fetch Headers class
whatwg-fetch:
Object
whatwg-fetch Headers class
I found the same results for:
Safari 16.0 (17614.1.25.9.10, 17614)
Firefox 108.0.2
My test bench for Headers support is here. cross-fetch is also tested, as it relies on whatwg-fetch in the browser, yields yet another behavior.
The text was updated successfully, but these errors were encountered:
According to the Fetch documentation on MDN, the
headers
property of theoptions
parameter can be:However, according to an example for errors below, an array of arrays of strings can be accepted (provided the inner arrays are of length 2).
This header initializer option is supported by the Headers constructor parameter, which can be
Testing in Chrome 109.0.5414.87, I found an inconsistency between what is supported by
whatwg-fetch
and what is supported by Chrome's native Fetch API.whatwg-fetch
:I found the same results for:
My test bench for Headers support is here. cross-fetch is also tested, as it relies on whatwg-fetch in the browser, yields yet another behavior.
The text was updated successfully, but these errors were encountered: