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 (free) tools but haven’t had the chance. After a question on the Testers Slack, I realized I could do a short blog post on how …
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. via Wikipedia Cooper says “no way!” 😀 For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on …
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, given when an unexpected condition was encountered and no more specific message is suitable. via Wikipedia For the entire HTTP Status Coop series that’s been released …
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. Previously called “Request Entity Too Large”. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop …
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 request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.” via Wikipedia For …
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 request. via Wikipedia Clearly the request was *not* acceptable for Cooper… For the entire HTTP Status Coop series that’s been released so far, head over to …
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, …