Adam Taft wrote:
The biggest concern for me is that IOException is being eaten in the
client. So, for example, an illegal url or a host not found error is
being trapped, logged and then no other error is being thrown. Yuck.
There's no appropriate status code which can model a "host not found"
exception, because the status codes imply actual contact with the server.
i'm starting to agree that that its hard to get an appropriate status
code particularly since the request hasn't left the client side.
cheers
</jima>
