Results for http-responder

A minimal HTTP responder

Very simple http server following https://practicingruby.com/articles/implementing-an-http-file-server?u=2c59db4496 as a guide

Semantic Media Query Handling

Interacts with an HTTP service used to respond to an Amazon Alexa Skill request.

Modifies ActionController::Base such that, in production, ActionView::MissingTemplate exceptions are caught and an HTTP 406-Not Acceptable response is rendered.

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.

Module to help your objects that respond to http requests via a Rack env

Tom uses Goliath to dispatch HTTP requests to multiple other APIs (via Adapters) in parallel. In a next step, a Merger merges the result and responds to the clients request.

Respond error for requests include some offensive string, that may crash browsers

RightAgent provides a foundation for running an agent on a server to interface in a secure fashion with other agents in the RightScale system using RightNet, which operates in either HTTP or AMQP mode. When using HTTP, RightAgent makes requests to RightApi servers and receives requests using long-polling or WebSockets via the RightNet router. To respond to requests it posts to the HTTP router. When using AMQP, RightAgent uses RabbitMQ as the message bus and the RightNet router as the routing node to make requests; to receives requests routed to it by the RightNet router, it establishes a queue on startup. The packets are structured to invoke services in the agent represented by actors and methods. The RightAgent may respond to these requests with a result packet that the router then routes to the originator.

This is a drop-in replacement for the apparently no longer maintained hhvacation program included in the GNU Hosting Helper (http://hostingsoftware.net/) suite. It only operates on so called "virtual" vacation responds (i.e. they are kept in a MySQL database).

Rstreamor gives you the power to stream your files using the HTTP range requests defined in the HTTP/1.1. Range requests are an optional feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource) can respond as if it is a normal GET request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for full responses by caches that might not implement the feature.

Most JSON APIs have a limited number of respondes or outcomes. Microcon tries to separate HTTP related concerns from business logic and removes most of the mental clutter regarding JSON parsing, rendering and consistent API responses.

No description provided.

No description provided.