Gateway wrapper client for Net::HTTP

fluent plugin to accept multiple json/msgpack events in HTTP request

Simple Rack middleware for adding custom HTTP headers.

This gem offers a shim to connect Rails apps with a Bonsai Elasticsearch cluster. The official Elasticsearch gem package requires some minor configuration tweaks in order to work correctly with Bonsai (namely the client needs to be instantiated with the cluster location and HTTP authentication details), and the process can be somewhat complicated for users who are unfamiliar with the system. The bonsai-elasticsearch-rails gem automatically sets up the Elasticsearch client correctly so users don't need to worry about configuring it in their code or writing an initializer. In order for the gem to work correctly, the application needs an environment variable called `BONSAI_URL`, which is populated with the complete Bonsai Elaticsearch cluster URL, including the HTTP authentication. The cluster URL will follow this pattern: https://user1234:pass5678@cluster-slug-123.aws-region-X.bonsai.io/ On Heroku, this variable is created and populated automatically when Bonsai is added to the application. Heroku users therefore do not need to perform any additional configuration to connect to their cluster after adding the bonsai-elasticsearch-rails gem. Users who are self-hosting their Rails app will need to make sure this environment variable is present: export BONSAI_URL="https://user1234:pass5678@aws-region-X.bonsai.io/" The cluster URL is available via the Bonsai dashboard.

Add http authorization methods to Roda

Http interface for the Eye gem.

Fewer is a Rack endpoint to bundle and cache assets and help you make fewer HTTP requests. Fewer extracts and combines a list of assets encoded in the URL and serves the response with far-future HTTP caching headers.

Ruby HTTP client with streaming support for GZIP compressed streams and chunked transfer encoding. Also includes extensible OAuth support for Adobe and Twitter streaming APIs.

You can communicate with Dkron using a RESTful JSON API over HTTP. Dkron nodes usually listen on port `8080` for API requests. All examples in this section assume that you've found a running leader at `localhost:8080`. Dkron implements a RESTful JSON API over HTTP to communicate with software clients. Dkron listens in port `8080` by default. All examples in this section assume that you're using the default port. Default API responses are unformatted JSON add the `pretty=true` param to format the response.

Library for data lookup tools (eg: hiera/jerakia) for looking up data over HTTP APIs

Rack adapter used to modify HTTP Accept header

Simple library for HTTP Accept header parsing and ordering.

Fluentd input plugin for to get the http status

BubbleWrap's deprecated HTTP library

This library provides MessagePack-RPC via HTTP, jruby fork

Rails I18n Backend for Http APIs with etag-aware background polling and memory+[memcache] caching

Kronk is a command line swiss-army-knife for HTTP services. With Kronk, you easily parse and segregate data, run diffs between the parsed data from different queries, and easily replay logs and loadtest your HTTP applications. Kronk was made possible by the sponsoring of YP.com.

a simple interface to gather curl stats against an HTTP resource

ForwardSlash makes REST a first-class citizen of the Ruby programming language. Rather than forcing developers to write code that makes calls to URLs over HTTP, ForwardSlash lets you drop the URL right in your code - no more worrying about what HTTP is. This blog post explains it best: http://blog.sinjakli.co.uk/2016/04/04/forwardslash-taking-back-the-restful-operator/

Standard-compliant cache for async-http.