HTTP Status Codes

This is a list of HTTP response status codes. If you want a full list, please read the article on Wikipedia.

2xx Success

200 OK

Standard response for successful HTTP requests.

201 Created

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.

3xx Redirection

301 Moved Permanently

This and all future requests should be directed to the given URI.

302 Found

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.

401 Unauthorized

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

403 Forbidden

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.

410 Gone

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.

Get started icon

Get Started

New to the StormForger?
With these guides you’ll be up and running in no time!

FAQ icon

FAQ

Already took a look at our FAQs?

Support icon

Support

Are you stuck? Talk to us! We're humans.

We are using cookies to give you the best online experience. If you continue to use this site, you agree to our use of cookies. By declining we will disable all but strictly required cookies. Please see our privacy policy for more details.


Accept Decline