Libraries tagged by http-state
sujal/json-resp
0 Downloads
A class that returns formatted JSON response with HTTP status
squaresandbrackets/craft-status-code
16 Downloads
Returns the HTTP status code within twig templates
soloded/http-constant
716 Downloads
Http status code constant definition
snapshotpl/status-code
13699 Downloads
HTTP status code value object implementation in PHP
simplicer/http
83 Downloads
Library to manage HTTP status codes and their descriptions.
saverty/errors_handling
15 Downloads
Laravel Errors Handling allow you to manage errors codes. Sometimes HTTP status aren't enought. With this package you can create your own status with a short description to share it with your team.
piurafunk/docker-php
8 Downloads
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.40) is used. For example, calling `/info` is the same as calling `/v1.40/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 Base64 encoded (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..." } ```
phpwedge/httpstatus
13 Downloads
PhpWedge Http Status Code and Message package
php-psr-middleware/null-request-handler
14 Downloads
Null PHP PSR Request Handler that returns a new Response with the provided HTTP status.
person55/json-response
7 Downloads
Simple class with properly formatted json response with HTTP status
paulvl/http
17 Downloads
HTTP Status Codes
p2media/httpmonitoring
0 Downloads
An extension for the TYPO3 CMS which adds a backend module for monitoring the HTTP status code given out by sites.
optimistdigital/laravel-set-cache-headers
176 Downloads
This Laravel package is a bug fix for not caching successful responses, especially the ones with the HTTP status code 204 (No Content).
ngreyson/json-response
2 Downloads
A simple class that returns a properly formatted json response with HTTP status
netsilik/http
18 Downloads
Basic HTTP Status Code helper class.