Re: X-HTTP-Method-Override request header

Yes, Rails does this as well, via Rack::MethodOverrride[1].

I used to be very mad about this, but have come to realize it's not that
big of a deal. Basically, all these frameworks _also_ support the actual
HTTP methods, so if you're building a non-browser client, you can use
the actual methods to take advantage of their semantics. But, given that
all you need is GET and POST[2], and given that HTML still only allows
those two methods in a <form>, I don't think that it's a significant
problem. Yes, the semantics are degraded, but it's not _wrong_. What I
mean is, since POST has basically no semantics, it's a superset. It'd be
bad if POST were a subset: ie, if POST were idempotent but PUT were not,
there'd be a problem.

Ideally HTML would adopt the other methods, but others have already
pointed out the discussions around this and the problems with such a move.

1: https://github.com/rack/rack/blob/master/lib/rack/methodoverride.rb
2: http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post