Category: REST API Testing

Tenth in the HTTP Status Coop series is 406 Not Acceptable! The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the …

Ninth in the HTTP Status Coop series is 404 Not Found! The requested resource could not be found but may be available in the future. Subsequent requests by the client …

Eighth in the HTTP Status Coop series is 403 Forbidden! The request was valid, but the server is refusing action. The user might not have the necessary permissions for a …

Seventh in the HTTP Status Coop series is 400 Bad Request! The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, …

Sixth in the HTTP Status Coop series is 307 Temporary Redirect! In this case, the request should be repeated with another URI; however, future requests should still use the original …

Fifth in the HTTP Status Coop series – 305 Use Proxy! The requested resource is available only through a proxy, the address for which is provided in the response. Many …

Fourth post in the HTTP Status Coop series – 303 See Other! The response to the request can be found under another URI using the GET method. When received in response to …

Third post in the HTTP Status Coop series – 206 Partial Content! The server is delivering only part of the resource (byte serving) due to a range header sent by …

Second post in the HTTP Status Coops – 202 Accepted! The request has been accepted for processing, but the processing has not been completed. The request might or might not …

In going back over my Testing RESTful Web Services talk prior to presenting at Targeting Quality, I decided that the HTTP Status Cats I was using on one of my …