Hi, this seems reasonable, but could you expand a bit on the problem? What browsers? Why? Is there a spec somewhere for this behavior? Is it a bug in the browser?

Hi,

I don't really know the details and I can't find documentation confirming it but when I set the X-HTTP-Method-Override header in a request sent by Chrome it is received on the server side as X-Method-Override.

That's all I've got

Hm, that sounds odd, could you share the code? If we're going to add this sort of workaround I just want to make sure it's appropriate. What's the behavior in Firefox? Safari? Edge?

I've tried with Chrome, Safari and Postman and they all rename the X-HTTP-Method-Override header into X-Method-Override.

curl does not.

I tested this in Firefox and Chrome and just judging by the network tab it didn't exhibit the header rewrite. Could you maybe share a JS snippet that reproduces this?

Yea, in the network tab we see the header as is but we receive it renamed on the server side.

I am quite confused as well and I can't find any documentation on this matter 🤷

Could you maybe share a JS snippet that reproduces this?

We use https://openapi-generator.tech/docs/generators/typescript-rxjs to generate a client from openapi specs

But even so, X-Method-Override seems to be widely used as well (regardless of the issue mentioned here)

I'm not trying to be difficult here, just making sure we're making the right decision for the project, I'm sure you can understand 😁. Could you share some references for the use of the X-Method-Override in other software/proxies/clients?

I know this is an old one but I found a bug around the same code: #3688