httparty 0.4.4 and 0.4.5 differences

[whoisjake]

I wrote a small Twitter httparty client that used it's search features.

In development on my machine, 0.4.4 and 0.4.5 worked the same... When I deployed the application to Heroku, 0.4.4 works but 0.4.5 causes Twitter to return a 400 Bad Request.

I feel like a bad bug reporter since I don't have any sample code, it was basically the same as your twitter example but built for the search.

I would imagine it's something to do with how it builds the request. Not sure if anything has changed recently, but for some reason, whatever is machine specific in the request generation is causing errors on Heroku.

Steps to reproduce:

1. Used this: http://gist.github.com/178266
2. With 0.4, it returned results in dev mode and on Heroku.
3. With 0.4.5 it returns results in dev, but not on Heroku.

Expected:
I should get twitter search results.

Actual:
I get a 400 Bad Request

[jnunemaker]

Twitter search started recently requiring the user agent to be set. My guess is it is related to that. Please check the twitter mailing list, and the httparty google group before submitting tickets.