Discover published sets by community

Continue: The server has received the request headers, and the client should proceed to send the request body.

Switching Protocols: The requester has asked the server to switch protocols and the server has agreed to do so.

OK: The request has succeeded and the information returned in the response is from the actual server.

Created: The request has been fulfilled and has resulted in the creation of a new resource.

Accepted: The request has been accepted for processing, but the processing has not been completed.

No Content: The server successfully processed the request, but is not returning any content.

Moved Permanently: The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs.

Found: The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client should continue to use the Request-URI for future requests.

Not Modified: Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.

Bad Request: The server cannot or will not process the request due to an apparent client error.

Unauthorized: Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

Forbidden: The request was a valid request, but the server is refusing to respond to it.

Not Found: The requested resource could not be found but may be available again in the future.

Request Timeout: The server timed out waiting for the request to be sent by the client.

Gone: The resource requested is no longer available and will not be available again.

Internal Server Error: A generic error message, given when no more specific message is suitable.

Not Implemented: The server either does not recognize the request method, or it lacks the ability to fulfill the request.

Service Unavailable: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

Found: The HTTP response status code 302 Found is a common way of performing URL redirection.

Unprocessable Entity: The server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.

Too Many Requests: The user has sent too many requests in a given amount of time ('rate limiting').

Request Header Fields Too Large: The server is unwilling to process the request because its header fields are too large.

Unavailable For Legal Reasons: 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.

Insufficient Storage: The server is unable to store the representation needed to complete the request.

Network Authentication Required: Indicates that the client needs to authenticate to gain network access.

Partial Content: The server is delivering only part of the resource (byte serving) due to a range header sent by the client.

Use Proxy: The requested resource is available only through a proxy, the address for which is provided in the response.

I'm a teapot: The server refuses the attempt to brew coffee with a teapot.

Too Early: Indicates that the server is unwilling to risk processing a request that might be replayed, potentially causing damage, because it is too early to process.

Upgrade Required: The client should switch to a different protocol such as TLS/1.0 given in the Upgrade header field.

Not Implemented: The server does not support the functionality required to fulfill the request.

HTTP Version Not Supported: The server does not support the HTTP protocol version used in the request.

Already Reported: The members of a DAV binding have already been enumerated in a previous part of the (multistatus) response, and are not being included again.

IM Used: The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

Insufficient Storage (WebDAV): The server is unable to store the representation needed to complete the request.

Loop Detected (WebDAV): The server detected an infinite loop while processing the request.

Early Hints: Used to return some response headers before final HTTP message.

Use Proxy: The requested resource must be accessed through the proxy given by the Location field.

Gone: The server was a gateway or proxy and received an invalid response from the upstream server.

Payload Too Large: The request is larger than the server is willing or able to process.