HTTP Status Coop – 400 Bad Request
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, …
Category: Professional Stuff
HTTP Status Coop – 307 Temporary Redirect
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 …
HTTP Status Coop – 305 Use Proxy
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 Status Coop – 303 See Other
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 …
HTTP Status Coop – 206 Partial Content
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 …
HTTP Status Coop – 202 Accepted
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 …
Targeting Quality 2017 Recap
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 …
HTTP Status… Coops?
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 …
Kalamazoo X 2017 Recap
Holy shit. Another amazing Kalamazoo X. This year was even more special because I was honored to be asked to speak. To be honest, speaking at Kalamazoo X was on …
CodeMash 2017 Recaps
Another CodeMash here and gone. I got in around 450 tweets this year – seemed like I didn’t attend as many sessions. Here are the recaps (via Storify) for the …