A gem packaging of the HttpComponents HTTP Client 4.x for JRuby.

An HTTP/1.1 pipelining implementation atop Net::HTTP. A pipelined connection sends multiple requests to the HTTP server without waiting for the responses. The server will respond in-order.

A lightweight framework for doing http-connections in Ruby. Supports cookies, keep-alive, compressing and much more.

Instruments the http gem for distributed tracing

Configurable Ruby gem that replaces error pages with http.cat image

This gem is a Faraday middleware that manages mapping schemes(https,http) to each endpoints. You can switch http/https more easily.

A HTTP/REST Client to help you wrap APIs easily.

a lita handler that displays HTTP Status Cats using https://http.cat/

Ruby implementation of the HPACK (Header Compression for HTTP/2) standard available at http://http2.github.io/http2-spec/compression.html

Ruby client for HTTP API server for image thumbnailing, editing and format conversion.

parse pcap, then return http request and response

`git push` to https repo securely.

Makes http fun & JSON parsing fast! Also, makes consuming restful web services dead easy. Forked from HTTParty.

HTTP client api for Ruby.

Persistent HTTP connections for HTTParty using the persistent_http gem. Keep the party alive!

Library for the HTTP Authentication protocol (RFC 2617)

A low level implementation of the HTTP/2 protocol.

A low level implementation of the HTTP/1 protocol.

The HttpRecognizer receives streamed HTTP, and when it accumulates enough to identify that it's seen an HTTP header, it attempts to extract some basic information from it. This is not a parser, and it is woefully incomplete, but for many tasks it understands just enough HTTP to be useful.

MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby and a simple REST API (as shown below). MockServer Proxy is a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding). Both MockServer and the MockServer Proxy record all received requests so that it is possible to verify exactly what requests have been sent by the system under test.