Re: HTTP Re: Status Code For Overload


I have now added the two extra return codes to the specs at


I would also like a code for


if the server sends nonsense back to the client. Actually this code
is already in the library, but it has not been documented :-(


-- cheers --


> Let me elaborate a bit on John's message.
> He wants a couple of new HTTP status codes put provisionally
> into the spec.  I suggest you change
> http://info.cern.ch/hypertext/WWW/Protocols/HTTP/HTRESP.html
> to include them with a "Provisional -- under discussion"
> comment.  The meaning sas I see them are, assuming the 
> 502 and 503 have not been taken,
> Service overloaded now  502
> 	The server cannot process the request due to a
> 	high load (whether HTTP servicing or other requests).
> 	The implication is that this is a temporary condition
> 	which maybe alleviated at other times.
> Gateway timeout 503  (Is this right John?)
> 	This is equivalent to Internal Error 500, but in the case of
> 	a server which is in turn accessing some other service, this
> 	indicates that the respose from the other service did not
> 	return within a time that the gateway was prepared to wait.
> 	As from the point of view of the clientand the HTTP
> 	transaction the other service is hidden within the server,
> 	this maybe treated identically to Internal error 500,
> 	but has more diagnostic value.