HTTP Status Codes
2 minute read
HTTP Status Codes
This is a list of HTTP response status codes. If you want a full list, please read the article on Wikipedia.
Standard response for successful HTTP requests.
The request has been fulfilled, resulting in the creation of a new resource.
204 No Content
The server successfully processed the request and is not returning any content.
301 Moved Permanently
This and all future requests should be directed to the given URI.
The client is required to perform a temporary redirect (the original describing phrase was “Moved Temporarily”).
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.
4xx Client Error
400 Bad Request
The server cannot or will not process the request due to an apparent client error. A 4xx error can occure, if something within the test case is not correctly defined. You should check your session configuration and/or your request definitions in the test case.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
The request was a valid request, but the server is refusing to respond to it.
404 Not Found
The requested resource could not be found but may be available in the future.
405 Method Not Allowed
A request method is not supported for the requested resource.
Indicates that the resource requested is no longer available and will not be available again.
415 Unsupported Media Type
The request entity has a media type which the server or resource does not support.
5xx Server Error
500 Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. A 5xx error can occure, if something went wrong within your web service. You should check your internal web service logs and your server configuration.
501 Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503 Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance).
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.