Add support for non-GET requests

[mateusg]

This is a solution for #121. I needed this myself while running some perf tests this week, so I took the opportunity to patch the gem, clean up and add tests.

I also had to find a way to set the Content-Type header, because the request I was testing was a JSON request and the gem did not support setting that header through HTTP_ variables (looks like it's a restriction from Rack, actually).

Another thing I had to do was disable the CSRF protection before initializing the app. I did that because non-GET requests require an authenticity token and I couldn't find a way to generate a valid one from the Rails.application context. I'm open to suggestions.

I really appreciate the work you've done with this gem @schneems (and everyone else who has contributed), it has helped me so much to investigate and find the memory leaks. It felt like I had everything I needed in a single tool. 🙂👏

[lessless]

Hi guys! Any progress on this one? Can be useful for applications that doesn't have GET routes at all

[d4rky-pl]

Bump

[pftg]

Instead of extending running of curl, will it be better to allow to provide a path to some script that will be triggered, and encapsulate there all those curl or non curl commands?

[jodosha]

+1

[Judobob]

+1