HTTP Status Coop – 500 Internal Server Error
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 so far, head over to the HTTP Status Coop page on my blog!
HTTP Status Coop – 413 Request Entity Too Large
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 page on my blog!
HTTP Status Coop – 408 Request Timed Out
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 the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my blog!
HTTP Status Coop – 406 Not Acceptable
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 the HTTP Status Coop page on my blog!
HTTP Status Coop – 404 Not Found
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 blog!
HTTP Status Coop – 403 Forbidden
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 the HTTP Status Coop page on my blog!
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, 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 been released so far, head over to the HTTP Status Coop page on my blog!
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 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, a POST request should be repeated using another POST request.
via Wikipedia
My husband, lovingly redirecting Cooper out of the snow 😀
For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my blog!
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 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 custom Big Head (from Fathead) of Cooper, that sits at my desk! It’s my proxy for interacting with my dog while at work 😀
For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my blog!
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 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 URI.
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 blog!
