Monthly Archives: November 2017

HTTP Status Coop – 503 Service Unavailable

Fourteenth in the HTTP Status Coop series is 503 Service Unavailable!

503ServiceUnavailable_img.jpg

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 my blog!

Advertisements

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!

500internalServerError_img

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)!

413RequestEntityTooLarge_img

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!

408RequestTimedOut_img

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!

406NotAcceptable_img.jpg

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!