This traps networking errors and makes a noble effort to be informative.
Most, if not all, network errors will be due to either network failure or pointing at the wrong URL. This PR tries to catch those that result in hitting the wrong URL.
Server responds 400 BAD REQUEST:
$ bindle --server http://bindle.f1sh.ca:8080/v1 search
Server has encountered an error: The request could not be handled by the server. Verify your Bindle server URL
A networking error occurred during connection (e.g. wrong port, server disconnects abruptly):
$ bindle --server http://bindle.f1sh.ca/v1 search
Server has encountered an error: Protocol error. Verify the Bindle URL
This traps networking errors and makes a noble effort to be informative.
Most, if not all, network errors will be due to either network failure or pointing at the wrong URL. This PR tries to catch those that result in hitting the wrong URL.
Server responds 400 BAD REQUEST:
A networking error occurred during connection (e.g. wrong port, server disconnects abruptly):
Closes #231
Signed-off-by: Matt Butcher matt.butcher@microsoft.com