ডেভেলপার ইউটিলিটি

The server received the request headers; the client should send the request body.

The server agrees to switch protocols, e.g. WebSocket upgrade.

The server received the request and is processing it but has not finished.

Sends preload hints before the final response.

Request succeeded. The body contains the requested resource or operation result.

Resource created successfully. Typically used after POST.

Request accepted but processing is not yet complete.

Request succeeded but the response may be a modified copy.

Request succeeded with an empty response body.

Request succeeded; the client should reset the document view.

Server returns partial content for range requests.

WebDAV multi-status response with multiple status codes.

WebDAV: internal member already reported in a previous 207.

Server applied instance manipulations; response is the current instance representation.

Multiple possible responses; the client may choose one.

Resource permanently moved to a new URL.

Resource temporarily at a different URL.

Server redirects the client to another URI; use GET to fetch it.

Resource not modified; cached copy may be used.

Temporary redirect; request method and body unchanged.

Permanent redirect; request method and body unchanged.

Malformed request or cannot be understood by the server.

Authentication is required.

Reserved for future use (e.g. payment, digital payment).

Server understood the request but refuses to authorize it.

The server cannot find the requested resource.

The request method is not allowed for this resource.

Cannot produce a response matching the Accept header.

Client must authenticate with the proxy first.

Server timed out while waiting for the request.

Request conflicts with the current server state.

Resource existed but has been permanently removed.

Request requires a Content-Length header.

A precondition in the request headers was not met.

Request body exceeds server limits.

The request URI is too long.

Server does not support the request media type.

The range requested in the Range header is invalid.

Expect header expectation could not be met.

Server refuses to brew coffee because it is a teapot. (RFC 2324 easter egg)

Request was directed at a server unable to produce a response.

Well-formed request but semantic errors prevent processing.

WebDAV resource is locked.

WebDAV request failed because a dependent request failed.

Server is unwilling to process a request that might be replayed.

Server requires a protocol upgrade.

Request must include conditional headers.

Too many requests; rate limited.

Request header fields are too large.

Unavailable for legal reasons (e.g. censorship, copyright).

Unexpected server error; request could not be completed.

Server does not support the requested functionality.

Gateway or proxy received an invalid response from upstream.

Server temporarily unable to handle the request.

Gateway or proxy timed out waiting for upstream.

Server does not support the HTTP version used in the request.

Server has an internal configuration error.

WebDAV: insufficient storage space.

WebDAV: infinite loop detected.

Server requires further extensions to fulfill the request.

Client must authenticate to access the network.