Raised when the address family is invalid such as an address with an unsupported family, an address with an inconsistent family, or an address who’s family cannot be determined.
Default formatter for log messages.
Parent class for informational (1xx) HTTP response classes.
An informational response indicates that the request was received and understood.
References:
Response class for Created responses (status code 201).
The Created response indicates that the server has received and has fulfilled a request to create a new resource.
References:
Response class for Accepted responses (status code 202).
The Accepted response indicates that the server has received and is processing a request, but the processing has not yet been completed.
References:
Response class for Partial Content responses (status code 206).
The Partial Content response indicates that the server is delivering only part of the resource (byte serving) due to a Range header in the request.
References:
Response class for Multi-Status (WebDAV) responses (status code 207).
The Multi-Status (WebDAV) response indicates that the server has received the request, and that the message body can contain a number of separate response codes.
References:
Response class for Already Reported (WebDAV) responses (status code 208).
The Already Reported (WebDAV) response indicates that the server has received the request, and that the members of a DAV binding have already been enumerated in a preceding part of the (multi-status) response, and are not being included again.
References:
Response class for See Other responses (status code 303).
The response to the request can be found under another URI using the GET method.
References:
Response class for Request Timeout responses (status code 408).
The server timed out waiting for the request.
References:
Response class for Request Timeout responses (status code 408).
The server timed out waiting for the request.
References:
Response class for Length Required responses (status code 411).
The request did not specify the length of its content, which is required by the requested resource.
References:
Response class for Payload Too Large responses (status code 413).
The request is larger than the server is willing or able to process.
References:
Response class for Range Not Satisfiable responses (status code 416).
The request entity has a media type which the server or resource does not support.
References:
Response class for Range Not Satisfiable responses (status code 416).
The request entity has a media type which the server or resource does not support.
References:
Response class for Expectation Failed responses (status code 417).
The server cannot meet the requirements of the Expect request-header field.
References:
Response class for Request Header Fields Too Large responses (status code 431).
An individual header field is too large, or all the header fields collectively, are too large.
References:
Response class for Unavailable For Legal Reasons responses (status code 451).
A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.
References:
Response class for Internal Server Error responses (status code 500).
An unexpected condition was encountered and no more specific message is suitable.
References:
Response class for Not Implemented responses (status code 501).
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
References:
Response class for Bad Gateway responses (status code 502).
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
References:
Response class for Service Unavailable responses (status code 503).
The server cannot handle the request (because it is overloaded or down for maintenance).
References:
Response class for Variant Also Negotiates responses (status code 506).
Transparent content negotiation for the request results in a circular reference.
References: