2010-01-24 10:04:31 -05:00
= REST Client -- simple DSL for accessing HTTP and REST resources
2008-03-09 16:25:18 -04:00
2010-01-24 10:04:31 -05:00
A simple HTTP and REST client for Ruby, inspired by the Sinatra's microframework style
2008-06-21 00:09:44 -04:00
of specifying actions: get, put, post, delete.
2008-03-09 16:25:18 -04:00
2009-12-26 09:51:47 -05:00
== Usage: Raw URL
2008-03-09 16:25:18 -04:00
2008-03-09 16:31:52 -04:00
require 'rest_client'
2008-03-09 16:25:18 -04:00
2008-08-01 14:39:24 -04:00
RestClient.get 'http://example.com/resource'
2010-01-01 07:59:47 -05:00
2008-08-01 14:39:24 -04:00
RestClient.get 'https://user:password@example.com/private/resource'
2008-03-09 16:25:18 -04:00
2008-08-01 14:39:24 -04:00
RestClient.post 'http://example.com/resource', :param1 => 'one', :nested => { :param2 => 'two' }
2008-06-21 00:07:20 -04:00
2009-12-29 14:30:38 -05:00
RestClient.post "http://example.com/resource", { 'x' => 1 }.to_json, :content_type => :json, :accept => :json
2008-06-21 00:07:20 -04:00
RestClient.delete 'http://example.com/resource'
2009-12-26 09:51:47 -05:00
== Multipart
2008-03-09 16:25:18 -04:00
2008-07-23 16:16:05 -04:00
Yeah, that's right! This does multipart sends for you!
RestClient.post '/data', :myfile => File.new("/path/to/image.jpg")
This does two things for you:
* Auto-detects that you have a File value sends it as multipart
* Auto-detects the mime of the file and sets it in the HEAD of the payload for each entry
If you are sending params that do not contain a File object but the payload needs to be multipart then:
RestClient.post '/data', :foo => 'bar', :multipart => true
2009-12-26 09:51:47 -05:00
== Usage: ActiveResource-Style
2008-03-10 20:20:57 -04:00
2008-06-21 00:07:20 -04:00
resource = RestClient::Resource.new 'http://example.com/resource'
2008-03-10 20:20:57 -04:00
resource.get
2008-07-20 16:13:16 -04:00
private_resource = RestClient::Resource.new 'https://example.com/private/resource', 'user', 'pass'
2008-06-21 00:07:20 -04:00
private_resource.put File.read('pic.jpg'), :content_type => 'image/jpg'
2008-03-10 20:20:57 -04:00
2009-12-20 10:20:30 -05:00
See RestClient::Resource module docs for details.
2008-03-10 20:20:57 -04:00
2009-12-26 09:51:47 -05:00
== Usage: Resource Nesting
2008-06-21 00:07:20 -04:00
site = RestClient::Resource.new('http://example.com')
site['posts/1/comments'].post 'Good article.', :content_type => 'text/plain'
See RestClient::Resource docs for details.
2010-02-10 15:48:46 -05:00
== Exceptions (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
2010-01-22 15:04:49 -05:00
* for results code between 200 and 206 a RestClient::Response will be returned
2010-02-10 15:48:46 -05:00
* for results code 301 and 302 the redirection will be followed if the request is a get or a head
* for result code 303 the redirection will be followed and the request transformed into a get
2010-02-10 15:31:59 -05:00
* for other cases a RestClient::Exception holding the Response will be raised, a specific exception class will be thrown for know error codes
2010-01-22 15:04:49 -05:00
RestClient.get 'http://example.com/resource'
➔ RestClient::ResourceNotFound: RestClient::ResourceNotFound
begin
RestClient.get 'http://example.com/resource'
rescue => e
e.response
end
2010-02-01 12:12:21 -05:00
➔ 404 Resource Not Found | text/html 282 bytes
2010-01-22 15:04:49 -05:00
== Result handling
A block can be passed to the RestClient method, this block will then be called with the Response.
2010-02-10 15:31:59 -05:00
Response.return! can be called to invoke the default response's behavior.
2010-01-22 15:04:49 -05:00
# Don't raise exceptions but return the response
2010-02-10 15:31:59 -05:00
RestClient.get('http://example.com/resource'){|response| response }
2010-02-01 12:12:21 -05:00
➔ 404 Resource Not Found | text/html 282 bytes
2010-01-22 15:04:49 -05:00
# Manage a specific error code
2010-02-10 15:31:59 -05:00
RestClient.get('http://my-rest-service.com/resource'){ |response, &block|
2010-01-22 15:04:49 -05:00
case response.code
when 200
p "It worked !"
response
when 423
raise SomeCustomExceptionIfYouWant
else
2010-02-10 15:31:59 -05:00
response.return! &block
end
}
# Follow redirections for all request types and not only for get and head
RestClient.get('http://my-rest-service.com/resource'){ |response, &block|
2010-02-10 15:48:46 -05:00
if [301, 303].include? code
2010-02-10 15:31:59 -05:00
follow_redirection
else
response.return! &block
2010-01-22 15:04:49 -05:00
end
}
2010-01-24 10:04:31 -05:00
== Non-normalized URIs.
2010-01-24 10:07:21 -05:00
If you want to use non-normalized URIs, you can normalize them with the addressable gem (http://addressable.rubyforge.org/api/).
2010-01-24 10:04:31 -05:00
require 'addressable/uri'
RestClient.get(Addressable::URI.parse("http://www.詹姆斯.com/").normalize.to_str)
2009-12-26 09:51:47 -05:00
== Lower-level access
2009-12-17 15:27:40 -05:00
2009-12-20 10:20:30 -05:00
For cases not covered by the general API, you can use the RestClient::Resource class which provide a lower-level API, see the class' rdoc for more information.
2009-12-17 15:27:40 -05:00
2009-12-26 09:51:47 -05:00
== Shell
2008-03-09 16:25:18 -04:00
2008-07-20 16:13:16 -04:00
The restclient shell command gives an IRB session with RestClient already loaded:
2008-07-07 22:49:10 -04:00
2008-07-20 16:13:16 -04:00
$ restclient
2010-02-01 12:12:21 -05:00
>> RestClient.get 'http://example.com'
2008-03-09 16:25:18 -04:00
2008-07-20 16:13:16 -04:00
Specify a URL argument for get/post/put/delete on that resource:
2008-07-16 19:15:26 -04:00
2008-07-20 16:13:16 -04:00
$ restclient http://example.com
2010-02-01 12:12:21 -05:00
>> put '/resource', 'data'
2008-07-16 19:15:26 -04:00
2008-07-20 16:13:16 -04:00
Add a user and password for authenticated resources:
$ restclient https://example.com user pass
2010-02-01 12:12:21 -05:00
>> delete '/private/resource'
2008-07-20 16:13:16 -04:00
Create ~/.restclient for named sessions:
2008-07-16 19:15:26 -04:00
2008-07-20 16:13:16 -04:00
sinatra:
2008-08-01 14:48:56 -04:00
url: http://localhost:4567
2008-07-20 16:13:16 -04:00
rack:
2008-08-01 14:48:56 -04:00
url: http://localhost:9292
2008-07-20 16:13:16 -04:00
private_site:
2008-08-01 14:48:56 -04:00
url: http://example.com
username: user
password: pass
2008-07-16 19:15:26 -04:00
2008-07-20 16:13:16 -04:00
Then invoke:
$ restclient private_site
2009-12-26 09:51:47 -05:00
2010-01-25 12:14:05 -05:00
Use as a one-off, curl-style:
$ restclient get http://example.com/resource > output_body
$ restclient put http://example.com/resource < input_body
== Logging
To enable logging you can
* set RestClient.log with a ruby Logger
* or set an environment variable to avoid modifying the code (in this case you can use a file name, "stdout" or "stderr"):
$ RESTCLIENT_LOG=stdout path/to/my/program
Either produces logs like this:
RestClient.get "http://some/resource"
# => 200 OK | text/html 250 bytes
RestClient.put "http://some/resource", "payload"
# => 401 Unauthorized | application/xml 340 bytes
Note that these logs are valid Ruby, so you can paste them into the restclient
shell or a script to replay your sequence of rest calls.
== Proxy
All calls to RestClient, including Resources, will use the proxy specified by
RestClient.proxy:
RestClient.proxy = "http://proxy.example.com/"
RestClient.get "http://some/resource"
# => response from some/resource as proxied through proxy.example.com
Often the proxy url is set in an environment variable, so you can do this to
use whatever proxy the system is configured to use:
RestClient.proxy = ENV['http_proxy']
== Cookies
Request and Response objects know about HTTP cookies, and will automatically
extract and set headers for them as needed:
response = RestClient.get 'http://example.com/action_which_sets_session_id'
response.cookies
# => {"_applicatioN_session_id" => "1234"}
response2 = RestClient.post(
'http://localhost:3000/',
{:param1 => "foo"},
{:cookies => {:session_id => "1234"}}
)
# ...response body
== SSL Client Certificates
RestClient::Resource.new(
'https://example.com',
:ssl_client_cert => OpenSSL::X509::Certificate.new(File.read("cert.pem")),
:ssl_client_key => OpenSSL::PKey::RSA.new(File.read("key.pem"), "passphrase, if any"),
:ssl_ca_file => "ca_certificate.pem",
:verify_ssl => OpenSSL::SSL::VERIFY_PEER
).get
Self-signed certificates can be generated with the openssl command-line tool.
2009-12-26 09:51:47 -05:00
== Meta
2008-03-09 16:25:18 -04:00
2010-01-22 15:04:49 -05:00
Written by Adam Wiggins, major modifications by Blake Mizerany, maintained by Julien Kirch
2008-08-03 19:12:05 -04:00
2010-01-22 15:04:49 -05:00
Patches contributed by many, including Chris Anderson, Greg Borenstein, Ardekantur, Pedro Belo, Rafael Souza, Rick Olson, Aman Gupta, François Beausoleil and Nick Plante.
2008-03-20 21:29:39 -04:00
2008-03-09 16:25:18 -04:00
Released under the MIT License: http://www.opensource.org/licenses/mit-license.php
2009-12-28 12:00:00 -05:00
Main page: http://github.com/archiloque/rest-client
2008-03-09 16:25:18 -04:00
2009-12-28 12:00:00 -05:00
Rdoc: http://rdoc.info/projects/archiloque/rest-client
2008-03-09 16:43:48 -04:00
2009-12-09 12:51:48 -05:00
Mailing list: rest.client@librelist.com (send a mail to subscribe).
2009-12-26 04:18:38 -05:00
IRC: #rest-client at freenode