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 a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given …
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 the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. via …
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 be eventually acted upon, and may be disallowed when processing occurs. via Wikipedia I chose this photo because it both shows that Cooper was accepted into …
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 slides just didn’t feel right. I was already using my dog in my talk, so why not make some up? I’m calling them HTTP Status …