1
0
Fork 0
mirror of https://github.com/jnunemaker/httparty synced 2023-03-27 23:23:07 -04:00
🎉 Makes http fun again!
Find a file
2008-11-08 14:00:32 -05:00
config Made sure I got the manifest and gem stuff all right. 2008-07-28 16:50:17 -04:00
examples Prepped for 0.1.4 release. 2008-11-08 11:30:26 -05:00
lib Moving send_request and friends into HTTParty::Request 2008-11-08 13:59:57 -05:00
script Renamed to HTTParty which is way more fun and unique than boring old web. 2008-07-28 10:49:53 -04:00
spec Spec opts now uses progress format 2008-11-08 14:00:32 -05:00
tasks Updated for new release. Added rake task to help with prepping for release. 2008-08-09 15:20:32 -04:00
website Updated readme and website. 2008-07-31 00:29:17 -04:00
.gitignore Initial commit 2008-07-27 11:52:18 -04:00
History.txt Prepped for 0.1.4 release. 2008-11-08 11:30:26 -05:00
httparty.gemspec Prepped for 0.1.4 release. 2008-11-08 11:30:26 -05:00
License.txt Tweaking information and readme. 2008-07-28 13:20:03 -04:00
Manifest.txt Prepped for 0.1.4 release. 2008-11-08 11:30:26 -05:00
PostInstall.txt Adjusted post install. Tweaked example. Created gemspec for github. Uncommented extra dependencies in hoe. 2008-07-28 16:48:22 -04:00
Rakefile Added spec task and set it as default task. 2008-10-25 00:37:51 -04:00
README.txt Added doco for various request options. 2008-10-25 00:35:10 -04:00
setup.rb Initial commit 2008-07-27 11:52:18 -04:00

= httparty

== DESCRIPTION:

Makes http fun again!

== FEATURES/PROBLEMS:

* Easy get, post, put, delete requests
* Basic http authentication
* Default request query string parameters (ie: for api keys that are needed on each request)
* Automatic parsing of JSON and XML into ruby hashes based on response content-type

== SYNOPSIS:

The following is a simple example of wrapping Twitter's API for posting updates.

	class Twitter
	  include HTTParty
	  base_uri 'twitter.com'
	  basic_auth 'username', 'password'
	end

	Twitter.post('/statuses/update.json', :query => {:status => "It's an HTTParty and everyone is invited!"})

That is really it! The object returned is a ruby hash that is decoded from Twitter's json response. JSON parsing is used because of the .json extension in the path of the request. You can also explicitly set a format (see the examples). 

That works and all but what if you don't want to embed your username and password in the class? Below is an example to fix that:

	class Twitter
	  include HTTParty
	  base_uri 'twitter.com'

	  def initialize(u, p)
	    @auth = {:username => u, :password => p}
	  end

	  def post(text)
	    options = { :query => {:status => text}, :basic_auth => @auth }
	    self.class.post('/statuses/update.json', options)
	  end
	end
	
	Twitter.new('username', 'password').post("It's an HTTParty and everyone is invited!")

=== REQUEST OPTIONS

Each of the HTTP method (get, post, put and delete) each take a hash of options.
The following keys can be specified in the options:

headers::       A <tt>Hash</tt> of header key/value pairs
query::         A <tt>Hash</tt> of query key/value pairs
body::          The body of the request. If it's a <tt>Hash</tt>, it is
                converted into query-string format, otherwise it is sent
                as-is.
basic_auth::    A <tt>Hash</tt> containing keys for <tt>:username</tt> and
                <tt>:password</tt>.
no_follow::     Turns off automatic redirect following

== REQUIREMENTS:

* Active Support >= 2.1

== INSTALL:

* sudo gem install httparty