httparty
httparty copied to clipboard
jnunemaker
:tada: Makes http fun again!
After finding [this question](https://stackoverflow.com/questions/51836680/outgoing-ports-for-making-http-requests-from-ruby-on-rails-app/51837467#51837467), I found that whenever a local_port is specified, it will automatically assume that we try to bind to localhost, as per `getaddrinfo(3)`: If the AI_PASSIVE flag...
Hey guys, It seems that if we make a request with HTTParty.get("webcal://example.com/something?param=1").body The params are ignored. I tried to look into the code, it seems that when you convert the...
Previously we were experiencing the issue in #533, so I had us pinned to 0.14.0. Since that was fixed, I removed the pin and tested with 0.15.5. Now I'm getting:...
Delegating methods to other objects using method_missing in instances of HTTParty::Response is causing unexpected behaviour and has resulted in multiple issues. Work-arounds to specific issues have been successful but this...
We currently have a problem where a feed we want to fetch finally resolves to `127.0.0.1:80`. The address of the feed is http://www.jennstrends.com/feed which redirects to http://www.jennstrends.com/feed/. In a normal...
I've seen this happen enough to know it's an issue, but we can't recreate the issue with any regularity. The problem is that (in our case) some small percentage of...
When I've tried to use https://github.com/NARKOZ/gitlab gem, I needed to serialize TLS options to global variable. It is very ugly, so, I added `_path` option for `p12` and `pem` for...
If I am understanding, currently to access cookies you would need to do something like the following: ``` cookies = response.headers['Set-Cookie'] cookie_hash = CookieHash.new() cookie_hash.add_cookies(cookies) ``` In this scenario, the...
HTTParty::Response sometimes looks nil but isn't. This makes for some interesting consequences and strange code in order to deal with them: [1] pry(#Salesforce::Rest)> response => nil [2] pry(#Salesforce::Rest)> response.code =>...
Would expect the following to work, but it seems like once **verify: false** is passed in it "defaults" to 443 and seems to ignore the passed in port. **$ response...
