Carlos Fuentes

Hmm... We can draft something down the line while removing the interceptors. Like the idea, it is similar to what we have for `request` and other APIs. It feels quite...

Do you have an example at hand? I think can provide a better idea of the usage. But on top of my mind, is this is something that can be...

> One comment from me: with the [original change](https://github.com/nodejs/undici/pull/4158/commits/810d7c6d841f8afd1745d07b067b2b511c9b30ca) enabling 100 concurrent streams for the entire codebase might have uncovered some issues when multiplexing is in use. Tests might be...

I've been running benchmarks with different combinations and I'm finding a strong correlation between the `pipelining` (parallel requests send through the same `session` within `undici`) and the number of max...

Thanks for the report and the work already done! I believe that for handling these cases, the best is to use the `retry` callback to decide wether or not to...

The `retryFn` will just allow you to say when to retry or not, but won't be able to capture the body in your request, this is for what I suggested...

I believe it can be good to outline possible situations where is better to use `undici`'s APIs rather than `fetch` directly. Would you like to send a PR addressing that?

We can help you go through it to develop it, that's not an issue (in case you are interested)

Can you provide an [Minimum Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example) that isolates the issue you are describing?

Sorry but that's not enough to reproduce your use case, you mentioned proxy so maybe there might be the root cause as the request works accordingly. Any stack, error, message?