Not sure under which team envoy falls in. It isn't listed in SRE. We need help to figure out a solution for this to unblock the migration to node22 for cxserver.

Change #1190253 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/services/cxserver@master] Use undic request when HOST header needed

https://gerrit.wikimedia.org/r/1190253

I 've already replied in T394982#11201112, but I find it improbable that SRE will be implementing such a behavior to accommodate for the change in node.js fetch() API. The HTTP Host header is pretty important across the infrastructure. Rewriting other HTTP headers to it might make debugging and reasoning more difficult than needed.

In T404291#11201131, @akosiaris wrote:

I 've already replied in T394982#11201112, but I find it improbable that SRE will be implementing such a behavior to accommodate for the change in node.js fetch() API. The HTTP Host header is pretty important across the infrastructure. Rewriting other HTTP headers to it might make debugging and reasoning more difficult than needed.

I agree; it is unreasonable to think we should work around limitations that exist for good reasons on the fetch API in browsers, but that make no sense for a backend program. Because it will only get worse over time, and I don't believe it's the right approach to service-to-service communication.

Change #1190253 merged by jenkins-bot:

[mediawiki/services/cxserver@master] Use undici request instead of node fetch

https://gerrit.wikimedia.org/r/1190253