HTTP Status Map
Database to lookup http reasons from http response status code
HTTP response status codes
HTTP response status codes
Fetch middleware for throwing errors based on HTTP response status codes.
A lightweight utility for retrieving HTTP status codes, names, and descriptions. Easily validate, categorize, and manage HTTP responses with built-in methods for informational, success, redirection, client, and server error codes.
Tool to check frequently http response status
Simple and intuitive HTTP response status codes
Http response status codes manager
HTTP response status codes as errors
Package includes all Official HTTP Response Status Codes and others unofficial.
Provides the `HttpStatus` class for managing HTTP response status codes.
Constants for HTTP response status codes that indicate whether a specific HTTP request has been successfully completed
Timings for HTTP requests
A response-like object for mocking a Node.js HTTP response stream
A tiny package containing all HTTP response status codes from https://developer.mozilla.org/en-US/docs/Web/HTTP/Status.
Constants enumerating the HTTP status codes. Based on the Java Apache HttpStatus API.
Node.js final http responder
Execute a callback when a request closes, finishes, or errors
Decompress a HTTP response if needed
A simple object to represent an http response
HTTP and HTTPS modules that follow redirects.
HTTP server mocking and expectations library for Node.js
Node.js CORS middleware
Clean up your controller code by raising exceptions that generate responses with different HTTP status codes.
Clean up your controller code by raising exceptions that generate responses with different HTTP status codes.
Fluentd input plugin that responses with HTTP status 200. Can be used for elb healthcheck.
Adds HTTP status code and response headers emulation to Selenium drivers
Clean up your controller code by raising exceptions that generate responses with different HTTP status codes.
A library that provides a hash map with all HTTP response status codes
any request in the rack layer, returns any json response(Content-Type: application/json) and http status.
Like Mockoon, but worse. Returns sarcastic mock HTTP responses.
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.
Wraps the Phone Your Rep API up with an idiomatic Ruby bow. Easily construct requests with block syntax and receive a response with http status, headers, raw body, and ActiveRecord-esque objects that make data-querying easy (using the lazy_record gem).
 **Before beginning work it is necessary that:** * Your organization is registered and activated * You have participated in a kickoff meeting * The opening questionnaire has been filled out * You have your login and password. (Using it you get a unique session `token` that must be used in every request to API as param `jwt`) [Contact us](https://bookingpal.com/en/contact-us/) to be registered and get your credentials. All responses are returned as JSON. This document covers all the API calls and other methods that can be used to complete Razor-Cloud integration. It is important to note that all parameters are **case sensitive** in this document and should be used as documented. **Responses:** When a request is successful, a response body will typically be sent back in the form of a JSON object. An exception to this is when a DELETE request is processed, which will result in a successful `200` status and an empty response body.
# Introduction Welcome to the reference for the Lishogi API! Lishogi is free/libre, open-source shogi server forked from lichess powered by volunteers and donations. Currently this page is a work in progress, certain information here might be wrong and incorrect! Expect it to be done during 2022. - Get help in the [Lishogi Discord channel](https://discord.gg/YFtpMGg3rR) - [Contribute to this documentation on Github](https://github.com/WandererXII/lishogi/blob/master/public/doc/lishogi-api.yaml) - Check out [Lishogi widgets to embed in your website](https://lishogi.org/developers) ## Endpoint All requests go to `https://lishogi.org` (unless otherwise specified). ## Rate limiting All requests are rate limited using various strategies, to ensure the API remains responsive for everyone. Only make one request at a time. If you receive an HTTP response with a [429 status](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#429), please wait a full minute before resuming API usage. ## Streaming with ND-JSON Some API endpoints stream their responses as [Newline Delimited JSON a.k.a. **nd-json**](http://ndjson.org/), with one JSON object per line. Here's a [JavaScript utility function (for lichess)](https://gist.github.com/ornicar/a097406810939cf7be1df8ea30e94f3e) to help reading NDJSON streamed responses.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.