More user-friendly curl-like output in case of error

I really love HTTPie for the cases when everything works fine, but if HTTPie can’t establish connection by some reason then I always have to switch back to curl to perform troubleshooting

Example: http: error: ConnectionError: HTTPSConnectionPool(host='myhost', port=32075): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x6fffed76630>: Failed to establish a new connection: [Errno 13] Permission denied')) while doing OPTIONS request to URL: https://myhost:32075/

Whole error message displayed in one line with a lot of unclear diagnostics + Python’s stacktrace. Please make it more user-friendly/clear + modify formatting to improve readability Thanks!

[ebonnecab]

Yes! @jakubroztocil that makes sense to me. Thank you!

[jakubroztocil]

@juped @rch-liu @ebonnecab awesome!

I would start by manually triggering & identifying as many types of errors as possible (by connecting to non-existing servers, passing weird arguments, making requests while offline, …, be creative!).

For each error type for which it makes sense (for example, arguments errors are already handled by argparse), I‘d write a function that returns a useful string representation with enough context for the user. with these, I would create a mapping between error types and the corresponding function.

Then, I‘d update the current catch-all handling to first try to get a custom representation for the given error from the mapping, and only if that fails, I‘d print out the exception like we do now.

https://github.com/jakubroztocil/httpie/blob/7ee519ef46ed0a4280f431d0c14745ed8244621f/httpie/core.py#L96-L109

The style and formatting of the errors should be consistent (between the new as well as the already existing errors).

Each of the supported error types needs a test case:

https://github.com/jakubroztocil/httpie/blob/master/tests/test_errors.py

If anything, ask away!