2017 Recap & Looking Forward to 2018
2017 was eventful, to say the least. I submitted 8 talks to 6 conferences. I was accepted to 5 of those conferences, gave an extra talk at one of them …
2017 was eventful, to say the least. I submitted 8 talks to 6 conferences. I was accepted to 5 of those conferences, gave an extra talk at one of them …
I signed up for the C# Advent Calendar with this post – be sure to check out the rest of the blog posts in the calendar! This post assumes you’ve …
In my Testing RESTful Web Services talk, I touch on service virtualization briefly, and I include a short demo of using Fiddler‘s AutoResponder. I’ve been meaning to look into other …
Fourteenth in the HTTP Status Coop series is 503 Service Unavailable! The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. …
Lucky Thirteen, on a Monday the 13th, of the HTTP Status Coop series is 500 Internal Server Error! And no, I didn’t plan it that way! A generic error message, …
Twelfth in the HTTP Status Coop series is 413 Request Entity Too Large (or Payload Too Large)! The request is larger than the server is willing or able to process. …
Eleventh in the HTTP Status Coop series is 408 Request Timed Out! The server timed out waiting for the request. According to HTTP specifications: “The client did not produce a …
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 …