Karl Stoney

Decided to reopen this because I'm not sure if the issue is with prettier, or eslint, but it only manifests since eslint v9. https://github.com/Stono/eslint-19258 contains a reproduction

``` import express from 'express' import should from 'should' import { Agent, fetch } from 'undici' describe.only('undici', function () { it('headers timeouts', async () => { const app = express()...

@metcoder95 sorry for the ridiculously long delay getting back to you.... honestly i pinned undici and forgot about it :| I'm now trying to upgrade and running into this again,...

I suppose the question really is how much it matters. For my particular use case, not so much. However you could argue for someone who had these settings configured low...

I do believe it should at least be documented, perhaps also on the jsdoc for those config items to let people know about the resolution.

I think it's better written by somebody who understands the timer implementation and the intent of the change.

Fair enough, to be clear though the destination web servers don't support it either, and all seem to just ignore it. It's one of those interop type problems that causes...

@howardjohn I went down a few rabbitholes today with envoyfitlters to try and think about mitigations to this. At first I wondered if I could remove the header by mutating...

@howardjohn sussed it, it's when we have `h2UpgradePolicy: UPGRADE` in the `istio-test-app-2` `DestinationRule` - we get the 101 + 1s delay 🤷 Also worth noting that we have this envoyfilter...

This extremely hacky EnvoyFilter puts a plaster on it, basically allows TLS1.2 on both inbound and outbound listeners, but then uses some lua to look for the TLS connection upgrade...