This is the simple REST client for Calendar API V3. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Calendar API, but note that some services may provide a separate modern client that is easier to use.

HTTP ContentType header parser

Provide a single command interface to perform http/json requests. A spec helper to perform request against a fake server is also included.

Middleware that provides both file extension and HTTP_ACCEPT-type content negotiation for Rack applications

Stub HTTP responses

A simple Ruby wrapper for the CloudApp API. Uses HTTParty with a simple ActiveResource-like interface.

Rack middleware for rate-limiting incoming HTTP requests.

Wrapper around net/http to provide quick and dirty http access.

An HTTP library for Ruby that takes advantage of everything HTTP has to offer.

HTTP support for ROM

Microsoft Kiota Abstractions - Ruby abstractions for building library agnostic http client

Certificate authority that can be configured to make decisions about whether to autosign certificate signing requests for clients. This gem provides the protocol-agnostic library, which is expected to be used within something like an HTTP REST service.

Ruby gem to create HTTP Content-Disposition headers with proper escaping/encoding of filenames

Randomize user agents for HTTP/HTTPS requests per device type.

Get the file uploading progress.

Human-friendly DSL for building HTTP(s) clients in Ruby

Ruby library to work with HTTP archives

CouchRest provides a simple interface on top of CouchDB's RESTful HTTP API, as well as including some utility scripts for managing views and attachments.

Utility belt for the HttpHeader libraries

Save HTTP responses to give your tests a hint of reality. Responses are saved into your fixtures directory and are used for subsequent web requests until they expire.