My friend John suggested a few more HTTP responses that deserve to become panty status:
> 405 Method Not Allowed
> 412 Precondition Failed
> 417 Expectation Failed
Once your mind goes in that direction, every HTTP response code sounds dirty.
> 100 Continue
> 300 Multiple Choices
> 307 Temporary Redirect
...
By the time you're through with those, even "504 Gateway Time-out" sounds kinky.
Think about THAT next time you're debugging HTTP codes.
Subscribe to:
Post Comments (Atom)
1 comment:
HTTP/1.1 503 Service Unavailable
Retry-After: 60
Server: Spouse
Date: Fri, 21 Apr 2006 15:59:17 GMT
Content-Type: text/plain
I am currently unable to handle your request due to a
temporary overloading or maintenance of me. 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, you SHOULD
handle the response as it would for a 500 response.
Post a Comment