Explore tens of thousands of sets crafted by our community.
HTTP Status Codes
41
Flashcards
0/41
101
Switching Protocols: The requester has asked the server to switch protocols and the server has agreed to do so.
301
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.
202
Accepted: The request has been accepted for processing, but the processing has not been completed.
204
No Content: The server successfully processed the request, but is not returning any content.
100
Continue: The server has received the request headers, and the client should proceed to send the request body.
200
OK: The request has succeeded and the information returned in the response is from the actual server.
201
Created: The request has been fulfilled and has resulted in the creation of a new resource.
302
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.
401
Unauthorized: Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
410
Gone: The resource requested is no longer available and will not be available again.
501
Not Implemented: The server either does not recognize the request method, or it lacks the ability to fulfill the request.
408
Request Timeout: The server timed out waiting for the request to be sent by the client.
429
Too Many Requests: The user has sent too many requests in a given amount of time ('rate limiting').
503
Service Unavailable: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
451
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.
404
Not Found: The requested resource could not be found but may be available again in the future.
302
Found: The HTTP response status code 302 Found is a common way of performing URL redirection.
305
Use Proxy: The requested resource is available only through a proxy, the address for which is provided in the response.
426
Upgrade Required: The client should switch to a different protocol such as TLS/1.0 given in the Upgrade header field.
304
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.
208
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.
507
Insufficient Storage (WebDAV): The server is unable to store the representation needed to complete the request.
305
Use Proxy: The requested resource must be accessed through the proxy given by the Location field.
431
Request Header Fields Too Large: The server is unwilling to process the request because its header fields are too large.
413
Payload Too Large: The request is larger than the server is willing or able to process.
410
Gone: The server was a gateway or proxy and received an invalid response from the upstream server.
403
Forbidden: The request was a valid request, but the server is refusing to respond to it.
511
Network Authentication Required: Indicates that the client needs to authenticate to gain network access.
206
Partial Content: The server is delivering only part of the resource (byte serving) due to a range header sent by the client.
501
Not Implemented: The server does not support the functionality required to fulfill the request.
226
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.
505
HTTP Version Not Supported: The server does not support the HTTP protocol version used in the request.
414
URI Too Long: The URI provided was too long for the server to process.
507
Insufficient Storage: The server is unable to store the representation needed to complete the request.
400
Bad Request: The server cannot or will not process the request due to an apparent client error.
500
Internal Server Error: A generic error message, given when no more specific message is suitable.
508
Loop Detected (WebDAV): The server detected an infinite loop while processing the request.
422
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.
418
I'm a teapot: The server refuses the attempt to brew coffee with a teapot.
425
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.
103
Early Hints: Used to return some response headers before final HTTP message.
© Hypatia.Tech. 2024 All rights reserved.