@yanglaofish/fishtools 0.5.2 → 0.6.0

package/node_modules/undici/README.md

@@ -1,6 +1,6 @@
 # undici
 
-[![Node CI](https://github.com/nodejs/undici/actions/workflows/ci.yml/badge.svg)](https://github.com/nodejs/undici/actions/workflows/nodejs.yml) [![neostandard javascript style](https://img.shields.io/badge/neo-standard-7fffff?style=flat\&labelColor=ff80ff)](https://github.com/neostandard/neostandard) [![npm version](https://badge.fury.io/js/undici.svg)](https://badge.fury.io/js/undici) [![codecov](https://codecov.io/gh/nodejs/undici/branch/main/graph/badge.svg?token=yZL6LtXkOA)](https://codecov.io/gh/nodejs/undici)
+[![Node CI](https://github.com/nodejs/undici/actions/workflows/nodejs.yml/badge.svg)](https://github.com/nodejs/undici/actions/workflows/nodejs.yml) [![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=flat)](http://standardjs.com/) [![npm version](https://badge.fury.io/js/undici.svg)](https://badge.fury.io/js/undici) [![codecov](https://codecov.io/gh/nodejs/undici/branch/main/graph/badge.svg?token=yZL6LtXkOA)](https://codecov.io/gh/nodejs/undici)
 
 An HTTP/1.1 client, written from scratch for Node.js.
 
@@ -21,243 +21,45 @@ npm i undici
 
 ## Benchmarks
 
-The benchmark is a simple getting data [example](https://github.com/nodejs/undici/blob/main/benchmarks/benchmark.js) using
-50 TCP connections with a pipelining depth of 10 running on Node 24.14.1.
+The benchmark is a simple getting data [example](https://github.com/nodejs/undici/blob/main/benchmarks/benchmark.js) using a
+50 TCP connections with a pipelining depth of 10 running on Node 20.10.0.
+
+|       _Tests_       | _Samples_ |     _Result_     | _Tolerance_ | _Difference with slowest_ |
+| :-----------------: | :-------: | :--------------: | :---------: | :-----------------------: |
+|   undici - fetch    |    30     | 3704.43 req/sec  |  ± 2.95 %   |             -             |
+| http - no keepalive |    20     | 4275.30 req/sec  |  ± 2.60 %   |         + 15.41 %         |
+|     node-fetch      |    10     | 4759.42 req/sec  |  ± 0.87 %   |         + 28.48 %         |
+|       request       |    40     | 4803.37 req/sec  |  ± 2.77 %   |         + 29.67 %         |
+|        axios        |    45     | 4951.97 req/sec  |  ± 2.88 %   |         + 33.68 %         |
+|         got         |    10     | 5969.67 req/sec  |  ± 2.64 %   |         + 61.15 %         |
+|     superagent      |    10     | 9471.48 req/sec  |  ± 1.50 %   |        + 155.68 %         |
+|  http - keepalive   |    25     | 10327.49 req/sec |  ± 2.95 %   |        + 178.79 %         |
+|  undici - pipeline  |    10     | 15053.41 req/sec |  ± 1.63 %   |        + 306.36 %         |
+|  undici - request   |    10     | 19264.24 req/sec |  ± 1.74 %   |        + 420.03 %         |
+|   undici - stream   |    15     | 20317.29 req/sec |  ± 2.13 %   |        + 448.46 %         |
+|  undici - dispatch  |    10     | 24883.28 req/sec |  ± 1.54 %   |        + 571.72 %         |
+
+The benchmark is a simple sending data [example](https://github.com/nodejs/undici/blob/main/benchmarks/post-benchmark.js) using a
+50 TCP connections with a pipelining depth of 10 running on Node 20.10.0.
+
+|       _Tests_       | _Samples_ |    _Result_     | _Tolerance_ | _Difference with slowest_ |
+| :-----------------: | :-------: | :-------------: | :---------: | :-----------------------: |
+|   undici - fetch    |    20     | 1968.42 req/sec |  ± 2.63 %   |             -             |
+| http - no keepalive |    25     | 2330.30 req/sec |  ± 2.99 %   |         + 18.38 %         |
+|     node-fetch      |    20     | 2485.36 req/sec |  ± 2.70 %   |         + 26.26 %         |
+|         got         |    15     | 2787.68 req/sec |  ± 2.56 %   |         + 41.62 %         |
+|       request       |    30     | 2805.10 req/sec |  ± 2.59 %   |         + 42.50 %         |
+|        axios        |    10     | 3040.45 req/sec |  ± 1.72 %   |         + 54.46 %         |
+|     superagent      |    20     | 3358.29 req/sec |  ± 2.51 %   |         + 70.61 %         |
+|  http - keepalive   |    20     | 3477.94 req/sec |  ± 2.51 %   |         + 76.69 %         |
+|  undici - pipeline  |    25     | 3812.61 req/sec |  ± 2.80 %   |         + 93.69 %         |
+|  undici - request   |    10     | 6067.00 req/sec |  ± 0.94 %   |        + 208.22 %         |
+|   undici - stream   |    10     | 6391.61 req/sec |  ± 1.98 %   |        + 224.71 %         |
+|  undici - dispatch  |    10     | 6397.00 req/sec |  ± 1.48 %   |        + 224.98 %         |
 
-### HTTP/1.1
-
-```
-┌────────────────────────┬─────────┬────────────────────┬────────────┬─────────────────────────┐
-│  Tests                 │ Samples │ Result             │ Tolerance  │ Difference with slowest │
-├────────────────────────┼─────────┼────────────────────┼────────────┼─────────────────────────┤
-│  'node-fetch'          │ 50      │ '4711.86 req/sec'  │ '± 2.92 %' │ '-'                     │
-│  'undici - fetch'      │ 75      │ '5438.50 req/sec'  │ '± 2.97 %' │ '+ 15.42 %'             │
-│  'axios'               │ 45      │ '5448.08 req/sec'  │ '± 2.98 %' │ '+ 15.62 %'             │
-│  'request'             │ 65      │ '5809.63 req/sec'  │ '± 2.90 %' │ '+ 23.30 %'             │
-│  'http - no keepalive' │ 35      │ '5910.77 req/sec'  │ '± 2.87 %' │ '+ 25.44 %'             │
-│  'got'                 │ 50      │ '6047.80 req/sec'  │ '± 2.91 %' │ '+ 28.35 %'             │
-│  'superagent'          │ 60      │ '7534.53 req/sec'  │ '± 2.97 %' │ '+ 59.91 %'             │
-│  'http - keepalive'    │ 75      │ '9343.41 req/sec'  │ '± 2.90 %' │ '+ 98.30 %'             │
-│  'undici - pipeline'   │ 65      │ '13470.70 req/sec' │ '± 2.93 %' │ '+ 185.89 %'            │
-│  'undici - request'    │ 80      │ '16850.87 req/sec' │ '± 2.93 %' │ '+ 257.63 %'            │
-│  'undici - stream'     │ 101     │ '18488.56 req/sec' │ '± 3.81 %' │ '+ 292.38 %'            │
-│  'undici - dispatch'   │ 101     │ '20786.44 req/sec' │ '± 3.08 %' │ '+ 341.15 %'            │
-└────────────────────────┴─────────┴────────────────────┴────────────┴─────────────────────────┘
-```
-
-### HTTP/1.1 over HTTPS
-
-Using [benchmark-https.js](https://github.com/nodejs/undici/blob/main/benchmarks/benchmark-https.js) against an h1-over-TLS server (50 connections, pipelining depth 10, Node 24.14.1).
-
-```
-┌────────────────────────┬─────────┬───────────────────┬────────────┬─────────────────────────┐
-│  Tests                 │ Samples │ Result            │ Tolerance  │ Difference with slowest │
-├────────────────────────┼─────────┼───────────────────┼────────────┼─────────────────────────┤
-│  'https - no keepalive'│ 10      │ '1358.40 req/sec' │ '± 1.99 %' │ '-'                     │
-│  'undici - fetch'      │ 30      │ '3721.76 req/sec' │ '± 2.97 %' │ '+ 173.98 %'            │
-│  'https - keepalive'   │ 35      │ '5633.91 req/sec' │ '± 2.84 %' │ '+ 314.75 %'            │
-│  'undici - pipeline'   │ 15      │ '6254.05 req/sec' │ '± 2.80 %' │ '+ 360.40 %'            │
-│  'undici - request'    │ 25      │ '6669.80 req/sec' │ '± 2.73 %' │ '+ 391.01 %'            │
-│  'undici - stream'     │ 25      │ '7019.04 req/sec' │ '± 2.77 %' │ '+ 416.71 %'            │
-│  'undici - dispatch'   │ 20      │ '7361.85 req/sec' │ '± 2.90 %' │ '+ 441.95 %'            │
-└────────────────────────┴─────────┴───────────────────┴────────────┴─────────────────────────┘
-```
-
-### HTTP/2
-
-Using [benchmark-http2.js](https://github.com/nodejs/undici/blob/main/benchmarks/benchmark-http2.js) against an h2 server (50 connections, pipelining depth 10, Node 24.14.1).
-
-```
-┌────────────────────────┬─────────┬───────────────────┬────────────┬─────────────────────────┐
-│  Tests                 │ Samples │ Result            │ Tolerance  │ Difference with slowest │
-├────────────────────────┼─────────┼───────────────────┼────────────┼─────────────────────────┤
-│  'undici - fetch'      │ 45      │ '3499.03 req/sec' │ '± 2.93 %' │ '-'                     │
-│  'native - http2'      │ 25      │ '4904.58 req/sec' │ '± 2.81 %' │ '+ 40.17 %'             │
-│  'undici - pipeline'   │ 60      │ '5836.82 req/sec' │ '± 2.99 %' │ '+ 66.81 %'             │
-│  'undici - request'    │ 65      │ '6831.25 req/sec' │ '± 2.83 %' │ '+ 95.23 %'             │
-│  'undici - stream'     │ 55      │ '6874.30 req/sec' │ '± 2.91 %' │ '+ 96.46 %'             │
-│  'undici - dispatch'   │ 55      │ '7791.23 req/sec' │ '± 2.96 %' │ '+ 122.67 %'            │
-└────────────────────────┴─────────┴───────────────────┴────────────┴─────────────────────────┘
-```
-
-## Undici vs. Fetch
-
-### Overview
-
-Node.js includes a built-in `fetch()` implementation powered by undici starting from Node.js v18. However, there are important differences between using the built-in fetch and installing undici as a separate module.
-
-### Built-in Fetch (Node.js v18+)
-
-Node.js's built-in fetch is powered by a bundled version of undici:
-
-```js
-// Available globally in Node.js v18+
-const response = await fetch('https://api.example.com/data');
-const data = await response.json();
-
-// Check the bundled undici version
-console.log(process.versions.undici); // e.g., "5.28.4"
-```
-
-**Pros:**
-- No additional dependencies required
-- Works across different JavaScript runtimes
-- Automatic compression handling (gzip, deflate, br)
-- Built-in caching support (in development)
-
-**Cons:**
-- Limited to the undici version bundled with your Node.js version
-- Less control over connection pooling and advanced features
-- Error handling follows Web API standards (errors wrapped in `TypeError`)
-- Performance overhead due to Web Streams implementation
-
-### Undici Module
-
-Installing undici as a separate module gives you access to the latest features and APIs:
-
-```bash
-npm install undici
-```
-
-```js
-import { request, fetch, Agent, setGlobalDispatcher } from 'undici';
-
-// Use undici.request for maximum performance
-const { statusCode, headers, body } = await request('https://api.example.com/data');
-const data = await body.json();
-
-// Or use undici.fetch with custom configuration
-const agent = new Agent({ keepAliveTimeout: 10000 });
-setGlobalDispatcher(agent);
-const response = await fetch('https://api.example.com/data');
-```
-
-**Pros:**
-- Latest undici features and bug fixes
-- Access to advanced APIs (`request`, `stream`, `pipeline`)
-- Fine-grained control over connection pooling
-- Better error handling with clearer error messages
-- Superior performance, especially with `undici.request`
-- HTTP/1.1 pipelining support
-- Custom interceptors and middleware
-- Advanced features like `ProxyAgent`, `Socks5Agent`, `MockAgent`
-
-**Cons:**
-- Additional dependency to manage
-- Larger bundle size
-
-### When to Use Each
-
-#### Use Built-in Fetch When:
-- You want zero dependencies
-- Building isomorphic code that runs in browsers and Node.js
-- Publishing to npm and want to maximize compatibility with JS runtimes
-- Simple HTTP requests without advanced configuration
-- You're publishing to npm and you want to maximize compatiblity
-- You don't depend on features from a specific version of undici
-
-#### Use Undici Module When:
-- You need the latest undici features and performance improvements
-- You require advanced connection pooling configuration
-- You need APIs not available in the built-in fetch (`ProxyAgent`, `Socks5Agent`, `MockAgent`, etc.)
-- Performance is critical (use `undici.request` for maximum speed)
-- You want better error handling and debugging capabilities
-- You need HTTP/1.1 pipelining or advanced interceptors
-- You prefer decoupled protocol and API interfaces
-
-### Performance Comparison
-
-Based on benchmarks, here's the typical performance hierarchy:
-
-1. **`undici.request()`** - Fastest, most efficient
-2. **`undici.fetch()`** - Good performance, standard compliance
-3. **Node.js `http`/`https`** - Baseline performance
-
-### Migration Guide
-
-If you're currently using built-in fetch and want to migrate to undici:
-
-```js
-// Before: Built-in fetch
-const response = await fetch('https://api.example.com/data');
-
-// After: Undici fetch (drop-in replacement)
-import { fetch } from 'undici';
-const response = await fetch('https://api.example.com/data');
-
-// Or: Undici request (better performance)
-import { request } from 'undici';
-const { statusCode, body } = await request('https://api.example.com/data');
-const data = await body.json();
-```
-
-### Keep `fetch` and `FormData` together
-
-When you send a `FormData` body, keep `fetch` and `FormData` from the same
-implementation.
-
-Use one of these patterns:
-
-```js
-// Built-in globals
-const body = new FormData()
-body.set('name', 'some')
-await fetch('https://example.com', {
-  method: 'POST',
-  body
-})
-```
-
-```js
-// undici module imports
-import { fetch, FormData } from 'undici'
-
-const body = new FormData()
-body.set('name', 'some')
-await fetch('https://example.com', {
-  method: 'POST',
-  body
-})
-```
-
-If you want the installed `undici` package to provide the globals, call
-`install()` first:
-
-```js
-import { install } from 'undici'
-
-install()
-
-const body = new FormData()
-body.set('name', 'some')
-await fetch('https://example.com', {
-  method: 'POST',
-  body
-})
-```
-
-`install()` replaces the global `fetch`, `Headers`, `Response`, `Request`, and
-`FormData` implementations with undici's versions, so they all match. It also
-installs undici's `WebSocket`, `CloseEvent`, `ErrorEvent`, `MessageEvent`, and
-`EventSource` globals.
-
-Avoid mixing a global `FormData` with `undici.fetch()`, or `undici.FormData`
-with the built-in global `fetch()`.
-
-### Version Compatibility
-
-You can check which version of undici is bundled with your Node.js version:
-
-```js
-console.log(process.versions.undici);
-```
-
-Installing undici as a module allows you to use a newer version than what's bundled with Node.js, giving you access to the latest features and performance improvements.
 
 ## Quick Start
 
-### Basic Request
-
 ```js
 import { request } from 'undici'
 
@@ -276,94 +78,6 @@ for await (const data of body) { console.log('data', data) }
 console.log('trailers', trailers)
 ```
 
-### Using Cache Interceptor
-
-Undici provides a powerful HTTP caching interceptor that follows HTTP caching best practices. Here's how to use it:
-
-```js
-import { fetch, Agent, interceptors, cacheStores } from 'undici';
-
-// Create a client with cache interceptor
-const client = new Agent().compose(interceptors.cache({
-  // Optional: Configure cache store (defaults to MemoryCacheStore)
-  store: new cacheStores.MemoryCacheStore({
-    maxSize: 100 * 1024 * 1024, // 100MB
-    maxCount: 1000,
-    maxEntrySize: 5 * 1024 * 1024 // 5MB
-  }),
-  
-  // Optional: Specify which HTTP methods to cache (default: ['GET', 'HEAD'])
-  methods: ['GET', 'HEAD']
-}));
-
-// Set the global dispatcher to use our caching client
-setGlobalDispatcher(client);
-
-// Now all fetch requests will use the cache
-async function getData() {
-  const response = await fetch('https://api.example.com/data');
-  // The server should set appropriate Cache-Control headers in the response
-  // which the cache will respect based on the cache policy
-  return response.json();
-}
-
-// First request - fetches from origin
-const data1 = await getData();
-
-// Second request - served from cache if within max-age
-const data2 = await getData();
-```
-
-#### Key Features:
-- **Automatic Caching**: Respects `Cache-Control` and `Expires` headers
-- **Validation**: Supports `ETag` and `Last-Modified` validation
-- **Storage Options**: In-memory or persistent SQLite storage
-- **Flexible**: Configure cache size, TTL, and more
-
-## Global Installation
-
-Undici provides an `install()` function to add fetch-related and other web API classes to `globalThis`, making them available globally:
-
-```js
-import { install } from 'undici'
-
-// Install undici's global web APIs
-install()
-
-// Now you can use fetch classes globally without importing
-const response = await fetch('https://api.example.com/data')
-const data = await response.json()
-
-// All classes are available globally:
-const headers = new Headers([['content-type', 'application/json']])
-const request = new Request('https://example.com')
-const formData = new FormData()
-const ws = new WebSocket('wss://example.com')
-const eventSource = new EventSource('https://example.com/events')
-```
-
-The `install()` function adds the following classes to `globalThis`:
-
-- `fetch` - The fetch function
-- `Headers` - HTTP headers management
-- `Response` - HTTP response representation
-- `Request` - HTTP request representation
-- `FormData` - Form data handling
-- `WebSocket` - WebSocket client
-- `CloseEvent`, `ErrorEvent`, `MessageEvent` - WebSocket events
-- `EventSource` - Server-sent events client
-
-When you call `install()`, these globals come from the same undici
-implementation. For example, global `fetch` and global `FormData` will both be
-undici's versions, and `WebSocket` and `EventSource` will also come from
-undici, which is the recommended setup if you want to use undici through
-globals.
-
-This is useful for:
-- Polyfilling environments that don't have fetch
-- Ensuring consistent fetch behavior across different Node.js versions
-- Making undici's implementations available globally for libraries that expect them
-
 ## Body Mixins
 
 The `body` mixins are the most common way to format the request/response body. Mixins include:
@@ -377,18 +91,6 @@ The `body` mixins are the most common way to format the request/response body. M
 > [!NOTE]
 > The body returned from `undici.request` does not implement `.formData()`.
 
-> [!WARNING]
-> The body mixins `.arrayBuffer()`, `.blob()`, `.bytes()`, `.json()`, `.text()`,
-> and `.formData()` buffer the entire body in memory before returning. Where
-> applicable, they also decode or parse the payload and retain that
-> representation in memory. Calling these methods therefore means trusting that
-> the response body is small enough to fit in the available memory. Do not use
-> them for responses from untrusted or user-controlled sources. Instead, consume
-> the response body as a stream and enforce an application-specific size limit:
-> use `response.body` for fetch responses or the `body` returned by
-> `undici.request()`. For streaming decoded text, use `body.textStream()` on a
-> fetch `Request` or `Response`.
-
 Example usage:
 
 ```js
@@ -417,11 +119,6 @@ For more information about their behavior, please reference the body mixin from
 
 This section documents our most commonly used API methods. Additional APIs are documented in their own files within the [docs](./docs/) folder and are accessible via the navigation list on the left side of the docs site.
 
-For the top-level APIs below, the `url` argument supplies the request origin and
-path. Do not pass `origin` or `path` in the second `options` argument. The linked
-`Dispatcher` option types include those fields because dispatcher methods are
-lower-level APIs that do not receive a separate `url` argument.
-
 ### `undici.request([url, options]): Promise`
 
 Arguments:
@@ -430,12 +127,13 @@ Arguments:
 * **options** [`RequestOptions`](./docs/docs/api/Dispatcher.md#parameter-requestoptions)
   * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
   * **method** `String` - Default: `PUT` if `options.body`, otherwise `GET`
+  * **maxRedirections** `Integer` - Default: `0`
 
 Returns a promise with the result of the `Dispatcher.request` method.
 
 Calls `options.dispatcher.request(options)`.
 
-See [Dispatcher.request](./docs/docs/api/Dispatcher.md#dispatcherrequestoptions-callback) for more details, and [request examples](./docs/examples/README.md) for examples.
+See [Dispatcher.request](./docs/docs/api/Dispatcher.md#dispatcherrequestoptions-callback) for more details, and [request examples](./examples/README.md) for examples.
 
 ### `undici.stream([url, options, ]factory): Promise`
 
@@ -445,6 +143,7 @@ Arguments:
 * **options** [`StreamOptions`](./docs/docs/api/Dispatcher.md#parameter-streamoptions)
   * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
   * **method** `String` - Default: `PUT` if `options.body`, otherwise `GET`
+  * **maxRedirections** `Integer` - Default: `0`
 * **factory** `Dispatcher.stream.factory`
 
 Returns a promise with the result of the `Dispatcher.stream` method.
@@ -461,6 +160,7 @@ Arguments:
 * **options** [`PipelineOptions`](./docs/docs/api/Dispatcher.md#parameter-pipelineoptions)
   * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
   * **method** `String` - Default: `PUT` if `options.body`, otherwise `GET`
+  * **maxRedirections** `Integer` - Default: `0`
 * **handler** `Dispatcher.pipeline.handler`
 
 Returns: `stream.Duplex`
@@ -478,6 +178,7 @@ Arguments:
 * **url** `string | URL | UrlObject`
 * **options** [`ConnectOptions`](./docs/docs/api/Dispatcher.md#parameter-connectoptions)
   * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
+  * **maxRedirections** `Integer` - Default: `0`
 * **callback** `(err: Error | null, data: ConnectData | null) => void` (optional)
 
 Returns a promise with the result of the `Dispatcher.connect` method.
@@ -533,7 +234,7 @@ A body can be of the following types:
 - URLSearchParams
 - FormData
 
-In this implementation of fetch, ```request.body``` now accepts ```Async Iterables```. It is not present in the [Fetch Standard](https://fetch.spec.whatwg.org).
+In this implementation of fetch, ```request.body``` now accepts ```Async Iterables```. It is not present in the [Fetch Standard.](https://fetch.spec.whatwg.org)
 
 ```js
 import { fetch } from 'undici'
@@ -562,13 +263,13 @@ await fetch('http://example.com', { method: 'POST', body })
 
 #### `request.duplex`
 
-- `'half'`
+- half
 
-In this implementation of fetch, `request.duplex` must be set if `request.body` is `ReadableStream` or `Async Iterables`, however, even though the value must be set to `'half'`, it is actually a _full_ duplex. For more detail refer to the [Fetch Standard](https://fetch.spec.whatwg.org/#dom-requestinit-duplex).
+In this implementation of fetch, `request.duplex` must be set if `request.body` is `ReadableStream` or `Async Iterables`, however, fetch requests are currently always full duplex. For more detail refer to the [Fetch Standard.](https://fetch.spec.whatwg.org/#dom-requestinit-duplex).
 
 #### `response.body`
 
-Nodejs has two kinds of streams: [web streams](https://nodejs.org/api/webstreams.html), which follow the API of the WHATWG web standard found in browsers, and an older Node-specific [streams API](https://nodejs.org/api/stream.html). `response.body` returns a readable web stream. If you would prefer to work with a Node stream you can convert a web stream using `.fromWeb()`.
+Nodejs has two kinds of streams: [web streams](https://nodejs.org/dist/latest-v16.x/docs/api/webstreams.html), which follow the API of the WHATWG web standard found in browsers, and an older Node-specific [streams API](https://nodejs.org/api/stream.html). `response.body` returns a readable web stream. If you would prefer to work with a Node stream you can convert a web stream using `.fromWeb()`.
 
 ```js
 import { fetch } from 'undici'
@@ -579,44 +280,37 @@ const readableWebStream = response.body
 const readableNodeStream = Readable.fromWeb(readableWebStream)
 ```
 
-## Specification Compliance
+#### Specification Compliance
 
-This section documents parts of the [HTTP/1.1](https://www.rfc-editor.org/rfc/rfc9110.html) and [Fetch Standard](https://fetch.spec.whatwg.org) that Undici does
+This section documents parts of the [Fetch Standard](https://fetch.spec.whatwg.org) that Undici does
 not support or does not fully implement.
 
-#### CORS
-
-Unlike browsers, Undici does not implement CORS (Cross-Origin Resource Sharing) checks by default. This means:
-
-- No preflight requests are automatically sent for cross-origin requests
-- No validation of `Access-Control-Allow-Origin` headers is performed
-- Requests to any origin are allowed regardless of the source
-
-This behavior is intentional for server-side environments where CORS restrictions are typically unnecessary. If your application requires CORS-like protections, you will need to implement these checks manually.
-
-#### Garbage Collection
+##### Garbage Collection
 
 * https://fetch.spec.whatwg.org/#garbage-collection
 
 The [Fetch Standard](https://fetch.spec.whatwg.org) allows users to skip consuming the response body by relying on
-[garbage collection](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management#garbage_collection) to release connection resources.
+[garbage collection](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management#garbage_collection) to release connection resources. Undici does not do the same. Therefore, it is important to always either consume or cancel the response body.
 
 Garbage collection in Node is less aggressive and deterministic
 (due to the lack of clear idle periods that browsers have through the rendering refresh rate)
 which means that leaving the release of connection resources to the garbage collector can lead
 to excessive connection usage, reduced performance (due to less connection re-use), and even
 stalls or deadlocks when running out of connections.
-Therefore, __it is important to always either consume or cancel the response body anyway__.
 
 ```js
 // Do
-const { body, headers } = await fetch(url);
-for await (const chunk of body) {
-  // force consumption of body
-}
+const headers = await fetch(url)
+  .then(async res => {
+    for await (const chunk of res.body) {
+      // force consumption of body
+    }
+    return res.headers
+  })
 
 // Do not
-const { headers } = await fetch(url);
+const headers = await fetch(url)
+  .then(res => res.headers)
 ```
 
 However, if you want to get only headers, it might be better to use `HEAD` request method. Usage of this method will obviate the need for consumption or cancelling of the response body. See [MDN - HTTP - HTTP request methods - HEAD](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD) for more details.
@@ -626,18 +320,7 @@ const headers = await fetch(url, { method: 'HEAD' })
   .then(res => res.headers)
 ```
 
-Note that consuming the response body is _mandatory_ for `request`:
-
-```js
-// Do
-const { body, headers } = await request(url);
-await body.dump(); // force consumption of body
-
-// Do not
-const { headers } = await request(url);
-```
-
-#### Forbidden and Safelisted Header Names
+##### Forbidden and Safelisted Header Names
 
 * https://fetch.spec.whatwg.org/#cors-safelisted-response-header-name
 * https://fetch.spec.whatwg.org/#forbidden-header-name
@@ -661,6 +344,7 @@ Arguments:
 * **url** `string | URL | UrlObject`
 * **options** [`UpgradeOptions`](./docs/docs/api/Dispatcher.md#parameter-upgradeoptions)
   * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
+  * **maxRedirections** `Integer` - Default: `0`
 * **callback** `(error: Error | null, data: UpgradeData) => void` (optional)
 
 Returns a promise with the result of the `Dispatcher.upgrade` method.
@@ -673,14 +357,7 @@ See [Dispatcher.upgrade](./docs/docs/api/Dispatcher.md#dispatcherupgradeoptions-
 
 * dispatcher `Dispatcher`
 
-Sets the global dispatcher used by Common API Methods. Global dispatcher is shared among compatible undici modules,
-including undici that is bundled internally with node.js.
-
-Undici stores this dispatcher under `Symbol.for('undici.globalDispatcher.2')`.
-
-`setGlobalDispatcher()` also mirrors the configured dispatcher to
-`Symbol.for('undici.globalDispatcher.1')` using `Dispatcher1Wrapper`, so Node.js built-in `fetch`
-can keep using the legacy handler contract while Undici uses the new handler API.
+Sets the global dispatcher used by Common API Methods.
 
 ### `undici.getGlobalDispatcher()`
 
@@ -720,7 +397,12 @@ Returns: `URL`
 * **protocol** `string` (optional)
 * **search** `string` (optional)
 
-#### Expect
+## Specification Compliance
+
+This section documents parts of the HTTP/1.1 specification that Undici does
+not support or does not fully implement.
+
+### Expect
 
 Undici does not support the `Expect` request header field. The request
 body is  always immediately sent and the `100 Continue` response will be
@@ -728,12 +410,10 @@ ignored.
 
 Refs: https://tools.ietf.org/html/rfc7231#section-5.1.1
 
-#### Pipelining
+### Pipelining
 
 Undici will only use pipelining if configured with a `pipelining` factor
-greater than `1`. Only enable pipelining when the remote server is trusted.
-Also it is important to pass `blocking: false` to the request options to
-properly pipeline requests.
+greater than `1`.
 
 Undici always assumes that connections are persistent and will immediately
 pipeline requests, without checking whether the connection is persistent.
@@ -750,7 +430,7 @@ aborted.
 * Refs: https://tools.ietf.org/html/rfc2616#section-8.1.2.2
 * Refs: https://tools.ietf.org/html/rfc7230#section-6.3.2
 
-#### Manual Redirect
+### Manual Redirect
 
 Since it is not possible to manually follow an HTTP redirect on the server-side,
 Undici returns the actual response instead of an `opaqueredirect` filtered one
@@ -759,9 +439,9 @@ implementations in Deno and Cloudflare Workers.
 
 Refs: https://fetch.spec.whatwg.org/#atomic-http-redirect-handling
 
-### Workarounds
+## Workarounds
 
-#### Network address family autoselection.
+### Network address family autoselection.
 
 If you experience problem when connecting to a remote server that is resolved by your DNS servers to a IPv6 (AAAA record)
 first, there are chances that your local router or ISP might have problem connecting to IPv6 networks. In that case
@@ -779,8 +459,6 @@ and `undici.Agent`) which will enable the family autoselection algorithm when es
 * [__Matthew Aitken__](https://github.com/KhafraDev), <https://www.npmjs.com/~khaf>
 * [__Robert Nagy__](https://github.com/ronag), <https://www.npmjs.com/~ronag>
 * [__Szymon Marczak__](https://github.com/szmarczak), <https://www.npmjs.com/~szmarczak>
-
-## Past Collaborators
 * [__Tomas Della Vedova__](https://github.com/delvedor), <https://www.npmjs.com/~delvedor>
 
 ### Releasers
@@ -790,17 +468,6 @@ and `undici.Agent`) which will enable the family autoselection algorithm when es
 * [__Robert Nagy__](https://github.com/ronag), <https://www.npmjs.com/~ronag>
 * [__Matthew Aitken__](https://github.com/KhafraDev), <https://www.npmjs.com/~khaf>
 
-## Long Term Support
-
-Undici aligns with the Node.js LTS schedule. The following table shows the supported versions:
-
-| Undici Version | Bundled in Node.js | Node.js Versions Supported | End of Life |
-|----------------|--------------------|----------------------------|-------------|
-| 5.x            | 18.x               | ≥14.0 (tested: 14, 16, 18) | 2024-04-30  |
-| 6.x            | 20.x, 22.x         | ≥18.17 (tested: 18, 20, 21, 22) | 2027-04-30  |
-| 7.x            | 24.x               | ≥20.18.1 (tested: 20, 22, 24) | 2028-04-30  |
-| 8.x            | 26.x               | ≥22.19.0 (tested: 22, 24, 26) | 2029-04-30  |
-
 ## License
 
 MIT