Verify signed HTTP requests from Manifold

Gateway wrapper client for Net::HTTP

Replicate or record HTTP requests to your Rack application and replay them elsewhere or at another time.

Okay, minimalist implementations of common utilities in Ruby. E.g., HTTP fetchers.

Simple Rack middleware for adding custom HTTP headers.

MinHTTP allows one to send and receive raw HTTP requests. It's a very thin wrapper around EventMachine's connect method with some SSL validation added.

Adds manticore tracking for HTTP calls to Newrelic

Simple async HTTP crawler based on em-synchrony

a pure ruby http/2 client & server based on http-2

Allows for easy embedding of content from a remote HTTP server and exporting of the Rails HTML layout into another template.

Toggl provides a simple REST-style JSON API over standard HTTP - http://www.toggl.com

Minimal Http Threaded Server with Ryby: Haml, Coffeescript, SSE, AJAX -- well under 200 lines of code!

大众点评开放平台ruby版SDK-http://developer.dianping.com/app/api

network-client is a drop-in thin layer on top of Net::HTTP classes for JSON web requests with retry functionality and simple error handling

CORTO - your url shortner gem ----------------------------- - Yet another url shortner? corto is a ruby gem that shorten a URL for you and store the result in a SQLite3 database. Why the world needs another url shortener? Well, true to be told I don't know the answer and I'm pretty sure this code is far away from being revolutionary. However... corto is funniest! - Usage Using corto as standalone utility is straightforward. In case you want to shorten an url you just launch the program with the url as parameter. % bin/corto http://www.armoredcode.com % corto: http://www.armoredcode.com shrunk as ji5jnu Please note that you've to supply a valid URL, since internally it's parsed and rejected anything but HTTP and HTTPS verbs. % bin/corto funnystatementhere % corto: it seems funnystatementhere is not a valid url to shrink If you want to deflate a shrunk url, you have just to specify the '-d' flag this way. % bin/corto -d ji5jnu % corto: ji5jnu deflated is http://www.armoredcode.com Super easy, isn't it? Now, go ahead and shrink the web! - API A simple corto shortening session start with class initialization, optionally telling which SQLite3 database to use and then mastering the parameter. require 'corto' ... corto = Corto.new # we're now saying the gem we want to use it's internal database stored in db/corto.db s = corto.shrink('http://www.armoredcode.com') # s now stores the shrinked url that is already added to database if not present. # If you'll pass an invalid url to shrink(), nil will be returned instead Deflating a URL is super easy as well # The deflate process is quite straightforward as well d = corto.deflate(s) # d has now the deflated url or nil if that url was not found You can also count how many urls contained into db # If you want to know how many urls you have in your database, just call the count() method. puts 'Hey, I have stored ' + corto.count() + ' urls' And finally you can purge your db # Tired of your database and time for a massive clean has come? Let's purge the db. corto.purge # corto.count == 0 now - Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don’t break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. - Copyright Copyright © 2011 Paolo Perego. See LICENSE for details.

hubba - (yet) another (lite) GitHub HTTP API client / library

Super simple DSL style web framework on top of Rack. Makes real HTTP'ish REST services easy.

With this project you will able to analyse your external resources status. You will be able to configure wich database connection to check or all the http urls

A gem providing HMAC based authentication for HTTP

A standalone Rack Middleware application that authenticates a username/password against a devise-powered backend application before forwarding the original HTTP request to the same application. Authentication is done on *every* request, so it is advisable to use devise-proxy sparingly.