Raised when the address is an invalid length.
Parent class for client error (4xx) HTTP response classes.
A client error response indicates that the client may have caused an error.
References:
Parent class for server error (5xx) HTTP response classes.
A server error response indicates that the server failed to fulfill a request.
References:
Response class for Early Hints responses (status code 103).
The Early Hints indicates that the server has received and is processing the request, and contains certain headers; the final response is not available yet.
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 Payment Required responses (status code 402).
Reserved for future use.
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 URI Too Long responses (status code 414).
The URI provided was too long for the server 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 Upgrade Required responses (status code 426).
The client should switch to the protocol given in the Upgrade 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 Internal Server Error responses (status code 500).
An unexpected condition was encountered and no more specific message is suitable.
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 Gateway Timeout responses (status code 504).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
References:
Response class for Gateway Timeout responses (status code 504).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
References:
Response class for Variant Also Negotiates responses (status code 506).
Transparent content negotiation for the request results in a circular reference.
References:
Response class for Insufficient Storage (WebDAV) responses (status code 507).
The server is unable to store the representation needed to complete the request.
References: