# The Question List Covering 2026-06-07 to 2026-09-05 16 threads read this period, 16 of them new. Threads are counted per distinct account. Bots and pull requests are excluded. ## New this week ### 1 person: Can redirected requests preserve the original request body? (new) - got > got` starting from version 15 started dropping request body when followRedirect: true The comment is wrong in the source code https://github.com/sindresorhus/got/blob/ … > - [307 & 308 redirect should preserve body per RFC](https://github.com/sindresorhus/got/issues/2459), 2026-06-26 ### 1 person: Can default headers be omitted when sending to absolute URLs in extended clients? (new) - got > Node.js version: not executed locally; static check used Got `v15.0.7`, which declares Node.js `>=22` - OS & version: not OS-specific Got's documentation describes `prefixUrl` … > - [Default headers from an extended client are still sent when calling it with an absolute URL](https://github.com/sindresorhus/got/issues/2461), 2026-06-30 ### 1 person: Can the cancel method be bound when the handler returns a new promise? (new) - got > When a `handlers` entry returns a new promise (e.g. an async wrapper around `next(options)`), calling `.cancel()` on the returned request throws: TypeError: Cannot read … > - [promise.cancel throws "Cannot read private member #state" when a handler returns a new promise](https://github.com/sindresorhus/got/issues/2467), 2026-07-09 ### 1 person: Can retries happen immediately when the Retry-After header is zero? (new) - got > When a server responds with `Retry-After: 0` (integer seconds format), `got` aborts retries entirely and fails the request, instead of retrying immediately: In `source/ … > - [Bug: `Retry-After: 0` seconds aborts retries entirely instead of retrying immediately](https://github.com/sindresorhus/got/issues/2468), 2026-08-25 ### 1 person: Can connection refusals still be retried under Node.js 24.20.0+? (new) - got > Retries stop after 1 attempt on connection refusal under Node.js 24.20.0+, surfaced as generic `ERR_SOCKET_CLOSED_BEFORE_CONNECTION` instead of the real error (regression from … > - [Retries stop after 1 attempt on connection refusal under Node.js 24.20.0+, surfaced as generic ERR_SOCKET_CLOSED_BEFORE_CONNECTION instead of the real error (regression from n …](https://github.com/sindresorhus/got/issues/2469), 2026-08-27 ### 1 person: Can the 403 forbidden error introduced in version 16.0.0 with cookie jars be fixed? (new) - got > I updated to 16.0.0 and my requests stopped working returning a 403. This code used to work with 15.1.0: > - [Request failed with status code 403 (Forbidden) with v16.0.0](https://github.com/sindresorhus/got/issues/2472), 2026-08-31 ### 1 person: Can CI testing be added for support of Node.js 26? (new) - got > github/workflows/main.yml\](https://github.com/sindresorhus/got/blob/main/.github/workflows/main.yml) tests in Node.js 22 & 24 https://github.com/sindresorhus/got/blob/64f21e2a … > - [Add CI testing for Node.js 26](https://github.com/sindresorhus/got/issues/2473), 2026-09-01 ## got 7 standing asks ### 1 person: Can redirected requests preserve the original request body? (new) > got` starting from version 15 started dropping request body when followRedirect: true The comment is wrong in the source code https://github.com/sindresorhus/got/blob/ … > - [307 & 308 redirect should preserve body per RFC](https://github.com/sindresorhus/got/issues/2459), 2026-06-26 ### 1 person: Can default headers be omitted when sending to absolute URLs in extended clients? (new) > Node.js version: not executed locally; static check used Got `v15.0.7`, which declares Node.js `>=22` - OS & version: not OS-specific Got's documentation describes `prefixUrl` … > - [Default headers from an extended client are still sent when calling it with an absolute URL](https://github.com/sindresorhus/got/issues/2461), 2026-06-30 ### 1 person: Can the cancel method be bound when the handler returns a new promise? (new) > When a `handlers` entry returns a new promise (e.g. an async wrapper around `next(options)`), calling `.cancel()` on the returned request throws: TypeError: Cannot read … > - [promise.cancel throws "Cannot read private member #state" when a handler returns a new promise](https://github.com/sindresorhus/got/issues/2467), 2026-07-09 ### 1 person: Can retries happen immediately when the Retry-After header is zero? (new) > When a server responds with `Retry-After: 0` (integer seconds format), `got` aborts retries entirely and fails the request, instead of retrying immediately: In `source/ … > - [Bug: `Retry-After: 0` seconds aborts retries entirely instead of retrying immediately](https://github.com/sindresorhus/got/issues/2468), 2026-08-25 ### 1 person: Can connection refusals still be retried under Node.js 24.20.0+? (new) > Retries stop after 1 attempt on connection refusal under Node.js 24.20.0+, surfaced as generic `ERR_SOCKET_CLOSED_BEFORE_CONNECTION` instead of the real error (regression from … > - [Retries stop after 1 attempt on connection refusal under Node.js 24.20.0+, surfaced as generic ERR_SOCKET_CLOSED_BEFORE_CONNECTION instead of the real error (regression from n …](https://github.com/sindresorhus/got/issues/2469), 2026-08-27 ### 1 person: Can the 403 forbidden error introduced in version 16.0.0 with cookie jars be fixed? (new) > I updated to 16.0.0 and my requests stopped working returning a 403. This code used to work with 15.1.0: > - [Request failed with status code 403 (Forbidden) with v16.0.0](https://github.com/sindresorhus/got/issues/2472), 2026-08-31 ### 1 person: Can CI testing be added for support of Node.js 26? (new) > github/workflows/main.yml\](https://github.com/sindresorhus/got/blob/main/.github/workflows/main.yml) tests in Node.js 22 & 24 https://github.com/sindresorhus/got/blob/64f21e2a … > - [Add CI testing for Node.js 26](https://github.com/sindresorhus/got/issues/2473), 2026-09-01 ## The numbers behind this report Every line above counts DISTINCT people, never posts. Each is linked to the public page it came from, so you can check any of them in one click. - New this period: 16 - Read this period: 16 - Analysed: 16 - Maintainer posts excluded: 2 Source: GitHub. 16 threads analysed over 90 days. 2 posts by the project's own maintainers are excluded from every count.