Jamie Tanna 3db7a4eb36 Fix: URL Encode keys and values in URL encoded form data ... As noted in #687, the existing implementation of our querystring construction was not valid according to the HTTP/1.1 specification, which was noticed with an integration issue with Apache Tomcat. This affects both the generation of Query Strings, and URL encoded form parameters. The solution is to ensure that we always URL-encode the keys, as well as the values. It appears that the existing test we had for this, "returns a Rails style query string", was not actually quite testing what we thought it was, as we had not tested the rendering of the raw values, only the URL decoded ones. Closes #697.		2020-04-16 17:59:53 +01:00
..
httparty	Fix: URL Encode keys and values in URL encoded form data	2020-04-16 17:59:53 +01:00
httparty.rb	use correct rdoc format	2020-01-23 16:57:22 +01:00