fetch icon indicating copy to clipboard operation
fetch copied to clipboard

A window.fetch JavaScript polyfill.

Results 50 fetch issues
Sort by recently updated
recently updated
newest added

The Fetch Standard defines [special behaviour for `Set-Cookie` headers](https://fetch.spec.whatwg.org/#concept-header-list-sort-and-combine): > To **sort and combine** a [header list](https://fetch.spec.whatwg.org/#concept-header-list) list, run these steps. They return a [header list](https://fetch.spec.whatwg.org/#concept-header-list). > > 1. Let...

Bumps the github-actions group with 5 updates in the / directory: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `4.1.2` |...

dependencies
github_actions

The fetch standard says that `response.body` should be `null` or a `body`. https://fetch.spec.whatwg.org/#responses > A [response](https://fetch.spec.whatwg.org/#concept-response) has an associated body (null or a [body](https://fetch.spec.whatwg.org/#concept-body)). Unless stated otherwise it is null....

## What When the Accept header of the outgoing request is either `"text/plain"` or `"application/json"`, set the response type of the underlying XHR request to `"text"`. ## Why This polyfill...

The spec demands that an `AbortSignal's` `reason` be thrown if present. https://fetch.spec.whatwg.org/#deserialize-a-serialized-abort-reason

We came across a bug in our code where we expected `await fetch('https://example.com/a-large-file.zip', { method: 'HEAD' })` to just get the HTTP status code and not fetch the HTTP body...

Bumps the github-actions group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `4.1.2` |...

dependencies
github_actions

The description of this method can be found in https://fetch.spec.whatwg.org/#response-class.

Fixes #1384 Specification: https://fetch.spec.whatwg.org/#dom-headers-getsetcookie Why is this needed since the browsers doesn't expose `Set-Cookie`? React Native is using this polyfill to provide `fetch`, and it does expose the `Set-Cookie` header....

If Response() throws when fetch() is trying to resolve it'll throw an error that can't be handled. This change would catch the error when trying to resolve and instead reject...