Carlos Fuentes

I think refers to removing it from `buildConnector`. Not so sure we should do that, but maybe I'm overseeing something; happy to see the PR to validate

Tested with latest main without success: ```js const { fetch: undiciFetch } = require('undici') async function test (method) { const signal = AbortSignal.timeout(1000) const res = await method( 'https://httpbin.org/drip?duration=2&numbytes=10&code=200&delay=0', {...

I can reproduce the problem, tho I'm not able to find yet what is exactly the change. The Ajv instance is managed by `@fastify/ajv-compiler` and automatically adds `ajv-formats` if not...

I believe is partially achievable by extending [Ajv keywords](https://ajv.js.org/guide/user-keywords.html), nevertheless I see the potential of this as standalone plugin as well, not so convinced that should be added in core.

Nice work, I believe this can live as a standalone `npm` package that exposes this interceptor.

I can see an interceptor for authentication, but it will require to be generic rather than scoped to an specific technology. You can customize `RetryHandler` as you need 👍 And...

Got it, a mix of Retry and Proxy-Like agent; it could be a good package, not so sure of undici core is the place for that. It can make usage...

Great findings! Tho, I doubt the issue roots there; what you point out seems mostly the effect of another issue. It is possible that, when error rates arise there might...

>How can the matching be customized? For example, to match on some headers but not all, to ignore authentication tokens for example. In my app I had subsequent POST calls...

This is somehow expected; the dispatcher returned by `getGlobalDispatcher` is not compatible with the latest changes made to the interceptors. If changed from ```js setGlobalDispatcher(getGlobalDispatcher().compose(interceptors.cache())) ``` to ```js setGlobalDispatcher(new Agent().compose(interceptors.cache()))...