The message returned is already very clear Can't connect.. is oblviously client side: so why the choose of an error of the 5** class?
The message is being returned to you by the client in the absence of any status code from the server because it cannot connect. This doesn't mean that it's a problem with the client - the server could be down or unroutable or the DNS could be screwy or whatever. The 4xx set is for operations where the client is at fault: malformed requests, unauthorized or forbidden access, unsatisfiable negotiation requests and so on.
The HTTP spec defines response codes which the server should provide. An absence of a response at all from the server rather renders a response code irrelevant. I'd be happy for the code to be undefined in the client in such a scenario but 500 seems a reasonable compromise in the absence of anything better. Consider 500 to mean "the request did not complete due to reasons beyond our knowledge".
🦛
In reply to Re: LWP::UserAgent Client-Warning 500 against HTTP standards?
by hippo
in thread LWP::UserAgent Client-Warning 500 against HTTP standards?
by Discipulus
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |