rack/rack — pull request #447 by lancecarlson (2012-11-02 19:41:21+00:00)
Title: Revisit: `Rack::MethodOverride` should work also with GET request

Here was my reply to a closed ticket:

There is actually a use case for supporting this. If you want to release a JSONP API. Since JSONP calls are only GET, the only way around this imposed restriction is to either redirect or \
somehow override all incoming calls to simulate "POST" requests. I feel like at the very least, one should be allowed to allow GET calls...

See stripe's API for an example of this in the real world.

Are there any other reasons you can think of that would make supporting GET an issue?

I'd like to reopen #160 for discussion.

Also, I'm attaching a commit I made with tests. If there is any additional validation you would like me to do perhaps to verify that it's a jsonp request or something I will build it too. I want to make sure I'm not opening up some security hole or something.