Post

Yes! 🎉🎉🎉 But I'm asking myself how many servers and proxies and reverse proxies will fail to deal with this. If it's even a small percent, it will impede the adoption of this (really important and how come it hasn't happened yet) specification.

We already have a path for that! When PUT/PATCH/DELETE were added nearly every server and proxy had no support. So most everything got updated to utilize the X-HTTP-METHOD-OVERRIDE header with a POST. This lets things attempt one mechanism and fallback to what is supported.

25/11/24, 5:54 am0 reposts1 like

I would even go so far as to say adding a new http method is easier than adding a new protocol. HTTP/3 has had so many hurdles to clear 😅

Gil Tayar

@gil.tayar.org

TIL! What I didn't get from what I read about it is how do I know whether to use QUERY or "GET with X-HTTP-METHOD-OVERRIDE" when sending a request? Wait, but that won't help because GET isn't allowed a body.

You’d use POST with the override and a body. You would lose some of the enhanced features but would otherwise be ok. You’d only need this if some element of your stack didn’t support the method yet. Most things “just will” because arbitrary http method names technically are a thing.

Gil Tayar

@gil.tayar.org

Got it. But I'm less worried about my stack (which I can easily check) and more about firewalls and reverse proxies along the way misinterpreting this method. But it feels from your answer that prior experience with other methods shows that this is not a problem?