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 are permissible. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my …
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 resource, or may need an account of some sort. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to …
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, size too large, invalid request message framing, or deceptive request routing). via Wikipedia Cooper does *not* like hats… For the entire HTTP Status Coop series that’s …
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 URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, …
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 HTTP clients (such as Mozilla[26] and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons. via Wikipedia This is a photo of my …
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 …
I was lucky enough to be accepted to speak at Targeting Quality in Kitchener, ON this year, and had a great time out there! This was my first time speaking outside the US, so it felt like a big accomplishment even though it’s just 3 hours from home. I only attended 3 sessions, including the …
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 …