The actual HttpClient that does the work with the thinnest layer between you and the protocol. All exceptions and leaks are allowed to pass through since those are important when testing. It doesn’t pretend to be a full client, but instead is just enough client to track cookies, form proper HTTP requests, and return HttpResponse hashes with the results.

It’s designed so that you create one client, and then you work it with a minimum of parameters as you need. The initialize method lets you pass in defaults for most of the parameters you’ll need, and you can simple call the method you want and it’ll be translated to an HTTP method (client.get => GET, client.foobar = FOOBAR).

Here’s a few examples:

  client = HttpClient.new(:head => {"X-DefaultHeader" => "ONE"})
  resp = client.post("/test")
  resp = client.post("/test", :head => {"X-TestSend" => "Status"}, :body => "TEST BODY")
  resp = client.put("/testput", :query => {"q" => "test"}, :body => "SOME JUNK")
  client.reset

The HttpClient.reset call clears cookies that are maintained.

It uses method_missing to do the translation of .put to "PUT /testput HTTP/1.1" so you can get into trouble if you’re calling unknown methods on it. By default the methods are PUT, GET, POST, DELETE, HEAD. You can change the allowed methods by passing :allowed_methods => [:put, :get, ..] to the initialize for the object.

Notifications

You can register a "notifier" with the client that will get called when different events happen. Right now the Notifier class just has a few functions for the common parts of an HTTP request that each take a symbol and some extra parameters. See RFuzz::Notifier for more information.

Parameters

  :head => {K => V}  or {K => [V1,V2]}
  :query => {K => V} or {K => [V1,V2]}
  :body => "some body" (you must encode for now)
  :cookies => {K => V} or {K => [V1, V2]}
  :allowed_methods => [:put, :get, :post, :delete, :head]
  :notifier => Notifier.new
  :redirect => false (give it a number and it'll follow redirects for that count)