fetch

fetch copied to clipboard

https://fetch.spec.whatwg.org/commit-snapshots/9bb2ded94073377ec5d9b5e3cda391df6c769a0a/#responses > This is used to ensure to prevent a partial response [...] Either "to ensure" or "to prevent" should be dropped.

jub0bs

https://fetch.spec.whatwg.org/commit-snapshots/9bb2ded94073377ec5d9b5e3cda391df6c769a0a/#simple-header > unprivilaged API should be > unprivileged API

jub0bs

Add abort reason to abort fetch

25

Following on from https://github.com/whatwg/dom/pull/1027, this PR uses the AbortSignal's abort reason in the [abort fetch](https://fetch.spec.whatwg.org/#abort-fetch) algorithm. @annevk Does this look okay to you? /cc @yutakahirano, @domenic - [ ] At...

nidhijaju

#1022 We need to send the Origin header for same-origin CORS requests even with no-referrer. This is the current behavior of all browsers (https://wpt.fyi/results/fetch/origin/assorted.window.html?label=master&label=experimental&aligned) and not doing so [breaks the...

evilpie

Pass in response status to mark resource timing

1

These changes are to support addition of http response status code to Perfomance resource timing. Further details are available at https://github.com/w3c/resource-timing/pull/335 - [x] At least two implementers are interested (and...

abinpaul1

Add option to reject the fetch promise automatically after a certain time elapsed (with no API for arbitrary aborts)

23

I'd like an option to have a timeout/deadline for the server to respond, so that if the response doesn't arrive within a specified number of seconds, the fetch promise is...

kornelski

Update Note on Request Destination / CSP directive

4

https://fetch.spec.whatwg.org/#concept-request-destination shows the CSP directive for a specific destination. I think that list needs to be updated to Content Security Policy Level 3. For example the destination `"script"` should now...

evilpie

Editorial: Use controller for navigation redirect

4

Remove the existing navigation redirect, and allow the caller to use the controller to continue to the next redirect. This simplifies the navigation HTMLFETCH flow, as now there is a...

noamr

HTTP 101 response NOT for websockets

12

Currently the spec says: > Any responses whose status is in the range 100 to 199, inclusive, and is not 101, are to be ignored, except for the purposes of...

yutakahirano

Add support for parsing a suffix byte range spec

1

Add support for parsing a range header in the suffix byte range spec form. - [ ] At least two implementers are interested (and none opposed): * … * …...

dlrobertson