JAWW (beta)

The ward is a factory for the Combine

503 Service Unavailable [closed]

10.5.4 503 Service Unavailable

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

10.5.1 500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

so, how the client SHOULD handle the 503 error response? — right, «User agents SHOULD display any included entity to the user»…

this reminds me a very old joke when we had to deal with an OS/360 on IBM mainframes. at those pre ‘point-and-click’ times these thingies were managed from the teletypes i.e. just a typewriter wired to console.

when something went wrong, they used to type a highly informative (to save trees) message on a paper roll which looked something like:

IEB042I: Impossible happened

since those devices had no CRT displays attached to them, to see an actual meaning of the error one had to riffle through a rather weighty volume of ‘Handbook of Error Messages’ (or how’d them called it).

imagine your surprise when at length having found the right page you could saw:

ERROR 421 see ERROR XYZ####

and of course, ‘ERROR XYZ####’ in its turn, eventually just sends you back to ERROR 421

Comments are closed.

%d bloggers like this: