Monthly Archives: September 2017

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 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 our family, and he’s accepted that he’ll be made to wear sweaters. His pig has also been accepted as his favorite toy…


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 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 keynotes – I missed one to center myself for my talk, and then I missed a session during my talk 😀

I storified my tweets from sessions I attended here:

I attended:


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 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 Coops because his name is Cooper. I’ll roll them out once a week or so here, in order. The list is incomplete as of now, but I’ll keep adding to them as long as Cooper keeps being goofy!

200 OK


Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.

via Wikipedia

This one was difficult because there are SO MANY PICTURES of Cooper that are him being 200 OK. He’s so expressive and has a huge smile. But this photo won out.