Libraries tagged by http exception
viserio/exception
1838 Downloads
The Viserio Exception package.
igniphp/exception
1657 Downloads
Common exceptions for inigphp packages.
charm/exceptions
0 Downloads
Various exception classes with some extra information such as HTTP Status Codes and HTTP Status Messages.
furiosojack/lara-exception
299 Downloads
Es un generador de excepciones, su fin es lanzar excepciones controladas al usuario con la posibilidad de generar log detallados al desarollador. El paquete es capaz de detectar una application/json de una peticion http por defecto. Este paquete entrega al usuario una vista en caso de ser http normal en donde se vera mensaje del error y un codigo de error, si la peticion es JSON el error sera devuelto en un resonse en formato JSON.
wedocreatives/wrike-php-guzzle
15 Downloads
HTTP Client and exception transformer adapter for Wrike PHP Library, based on Guzzle package
zibios/wrike-php-guzzle
6313 Downloads
HTTP Client and exception transformer adapter for Wrike PHP Library, based on Guzzle package
heedworks/loggr-php
419 Downloads
PSR-0 compliant version of the Loggr PHP agent (http://github.com/loggr/loggr-php)
germania-kg/middleware
89 Downloads
Collection of PSR-15 and PSR-7-style middleware
shopery/error-bundle
8662 Downloads
Manage what exceptions you throw and convert them to HttpException ones
holystix/error-reporter
489 Downloads
Reporting exceptions over HTTP to remote address
cube-agency/error-reporter
8696 Downloads
Reporting exceptions over HTTP to remote address
wnikk/laravel-flexible-throttle
0 Downloads
A Laravel middleware for advanced throttle based on IP, session, HTTP status codes, and exceptions. This package provides flexible and customizable protection for your application against brute force, password or scanning abuse and ensures fair use.
grifix/error-presenter-bundle
132 Downloads
Converts exceptions to proper http responses
lalu/jer
52 Downloads
A laravel/lumen package for structing API exception response in JSON followed http://jsonapi.org/
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..." } ```