Post

Gil Tayar
@gil.tayar.org

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.

Chris Thoburn
@runspired.com

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.

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.

Chris Thoburn
@runspired.com

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.

0 reposts0 likes

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?

Chris Thoburn
@runspired.com

more often than not things that are supposed to relay will relay. Its definitely the corporate firewall/proxy situation that has the highest chance of blocking something it doesn't know which is where falling back to tunneling comes in.