Known exceptions that might occur when using a backend. Currently this covers:
connect exceptions: when a connection (tcp socket) can't be established to the target host
read exceptions: when a connection has been established, but there's any kind of problem receiving or handling
the response (e.g. a broken socket or a deserialization error)
In general, it's safe to assume that the request hasn't been sent in case of connect exceptions. With read
exceptions, the target host might or might have not received and processed the request.
The SttpBackend.send methods might also throw other exceptions, due to programming errors, bugs in the
underlying implementations, bugs in sttp or an uncovered exception.
Known exceptions that might occur when using a backend. Currently this covers:
In general, it's safe to assume that the request hasn't been sent in case of connect exceptions. With read exceptions, the target host might or might have not received and processed the request.
The SttpBackend.send methods might also throw other exceptions, due to programming errors, bugs in the underlying implementations, bugs in sttp or an uncovered exception.