Libraries tagged by httpstatus

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

return HTTP status

Go to Download

Get status description from http status code

Go to Download

Http status code

Go to Download

Package provides an enumeration of standard HTTP status codes along with convenient methods for working with them.

Go to Download

Grinet NotFoundCode is a Magento 2 module that allows you to change the default 404 HTTP status code to a different one (such as 410) for SEO purposes.

Go to Download

Laravel Health Check 200 is a Health Check which checks for a 200 HTTP Status Code

Go to Download

A simple class that returns a propely formatted json response with HTTP status

Go to Download

Scan Urls http status

Go to Download

This module provide handler in order to support multiple Exceptions for 4xx or 5xx HTTP status code

Go to Download

A simple class that returnas a properly formatted json response with HTTP status

Go to Download

A simple class that returns a properly formatted json response with HTTP status

Go to Download

Simply return the http status of a url

Go to Download

Various exception classes with some extra information such as HTTP Status Codes and HTTP Status Messages.

Go to Download

A simple class that returns a properly formatted json response with HTTP status

Go to Download