http

Table of Contents

Classes

Error400

The HTTP 400 Bad Request client error response status code indicates that the server would not process the request due to something the server considered to be a client error.

Error401

The HTTP 401 Unauthorized client error response status code indicates that a request was not successful because it lacks valid authentication credentials for the requested resource.

Error402

The HTTP 402 Payment Required client error response status code is a nonstandard response status code reserved for future use.

Error403

The HTTP 403 Forbidden client error response status code indicates that the server understood the request but refuses to authorize it.

Error404

The HTTP 404 Not Found client error response status code indicates that the server cannot find the requested resource. Links that lead to a 404 page are often called broken or dead links and can be subject to link rot.

Error405

The HTTP 405 Method Not Allowed client error response status code indicates that the server knows the request method, but the target resource doesn't support this method.

Error406

The HTTP 406 Not Acceptable client error response status code indicates that the server could not produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers and that the server was unwilling to supply a default representation.

Error407

The HTTP 407 Proxy Authentication Required client error response status code indicates that the request did not succeed because it lacks valid authentication credentials for the proxy server that sits between the client and the server with access to the requested resource.

Error408

The HTTP 408 Request Timeout client error response status code indicates that the server would like to shut down this unused connection. It is sent on an idle connection by some servers, even without any previous request by the client.

Error409

The HTTP 409 Conflict client error response status code indicates a request conflict with the current state of the target resource.

Error410

The HTTP 410 Gone client error response status code indicates that the target resource is no longer available at the origin server and that this condition is likely to be permanent.

Error411

The HTTP 411 Length Required client error response status code indicates that the server refused to accept the request without a defined Content-Length header.

Error412

The HTTP 412 Precondition Failed client error response status code indicates that access to the target resource was denied. This happens with conditional requests when the condition defined by the If-Unmodified-Since or If-None-Match headers is not fulfilled.

Error413

The HTTP 413 Content Too Large client error response status code indicates that the request entity was larger than limits defined by the server. The server might close the connection or return a Retry-After header field.

Error414

The HTTP 414 URI Too Long client error response status code indicates that a URI requested by the client was longer than the server is willing to interpret.

Error415

The HTTP 415 Unsupported Media Type client error response status code indicates that the server refused to accept the request because the message content format is not supported.

Error416

The HTTP 416 Range Not Satisfiable client error response status code indicates that a server could not serve the requested ranges. The most likely reason is that the document doesn't contain such ranges, or that the Range header value, though syntactically correct, doesn't make sense.

Error417

The HTTP 417 Expectation Failed client error response status code indicates that the expectation given in the request's Expect header could not be met.

Error418

The HTTP 418 I'm a teapot status code indicates that the server refuses to brew coffee because it is, permanently, a teapot. This is a reference to the Hyper Text Coffee Pot Control Protocol (an April Fools' joke from 1998) and is not expected to be implemented by actual HTTP servers.

Error421

The HTTP 421 Misdirected Request client error response status code indicates that the request was directed to a server that is not able to produce a response.

Error422

The HTTP 422 Unprocessable Content client error response status code indicates that the server understood the content type of the request content, and the syntax of the request content was correct, but it was unable to process the contained instructions.

Error423

The HTTP 423 Locked client error response status code indicates that a resource is locked, meaning it can't be accessed. Its response body should contain information in WebDAV format.

Error424

The HTTP 424 Failed Dependency client error response status code indicates that the method could not be performed on the resource because the requested action depended on another action, and that action failed.

Error425

The HTTP 425 Too Early client error response status code indicates that the server was unwilling to risk processing a request that might be replayed to avoid potential replay attacks.

Error426

The HTTP 426 Upgrade Required client error response status code indicates that the server refuses to perform the request using the current protocol but might do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocols.

Error428

The HTTP 428 Precondition Required client error response status code indicates that the server requires the request to be conditional. Typically, this means that a required precondition header, such as If-Match, is missing.

Error429

The HTTP 429 Too Many Requests client error response status code indicates the user has sent too many requests in a given amount of time. This is intended for use with rate-limiting schemes and may include a Retry-After header indicating how long to wait before making a new request.

Error431

The HTTP 431 Request Header Fields Too Large client error response status code indicates that the server refuses to process the request because the request's HTTP headers are too long. The request may be resubmitted after reducing the size of the request headers.

Error451

The HTTP 451 Unavailable For Legal Reasons client error response status code indicates that the user requested a resource that is not available due to legal reasons, such as a web page for which a legal action has been issued.

Error500

The HTTP 500 Internal Server Error server error response status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

Error501

The HTTP 501 Not Implemented server error response status code indicates that the server does not support the functionality required to fulfill the request.

Error502

The HTTP 502 Bad Gateway server error response status code indicates that a server was acting as a gateway or proxy and that it received an invalid response from the upstream server.

Error503

The HTTP 503 Service Unavailable server error response status code indicates that the server is not ready to handle the request. Common causes are that the server is down for maintenance or is overloaded. A Retry-After header may indicate how long to wait before retrying.

Error504

The HTTP 504 Gateway Timeout server error response status code indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server in order to complete the request.

Error505

The HTTP 505 HTTP Version Not Supported server error response status code indicates that the HTTP version used in the request is not supported by the server.

Error506

The HTTP 506 Variant Also Negotiates server error response status code is returned during content negotiation when there is a recursive loop in the process of selecting a resource representation.

Error507

The HTTP 507 Insufficient Storage server error response status code indicates that an action could not be performed because the server does not have enough available storage to successfully complete the request.

Error508

The HTTP 508 Loop Detected server error response status code indicates that the server terminated an operation because it encountered an infinite loop while processing a request with Depth: infinity.

Error510

The HTTP 510 Not Extended server error response status code is sent when the client request declares an HTTP extension that should be used to process the request, but the extension is not supported by the server.

Error511

The HTTP 511 Network Authentication Required server error response status code indicates that the client needs to authenticate to gain network access. This status is not generated by origin servers, but by intercepting proxies that control access to the network (for example, captive portals).

HttpException

Base class for all HTTP error exceptions.