fix: Order of reqwest error handling

Inspect timeout errors first as they can originate from other locations.
In this particular case a request timeout would always return an
unexpected EOF since we handled body errors before timeout.

Author: LeanderBB

Cargo.toml

@@ -1,7 +1,7 @@
 [package]
 name = "proton-api-rs"
 authors = ["Leander Beernaert <lbb-dev@pm.me>"]
-version = "0.5.2"
+version = "0.5.3"
 edition = "2021"
 license = "AGPL-3.0-only"
 description = "Unofficial implemention of proton REST API in rust"

src/client/http_client/reqwest_client.rs

@@ -180,6 +180,12 @@ impl From<reqwest::Error> for RequestError {
 
 impl From<reqwest::Error> for HttpClientError {
     fn from(value: reqwest::Error) -> Self {
+        // Check timeout before all other errors as it can be produced by multiple
+        // reqwest error kinds.
+        if value.is_timeout() {
+            return HttpClientError::Timeout(anyhow::Error::new(value));
+        }
+
         #[cfg(not(target_arch = "wasm32"))]
         if value.is_connect() {
             return HttpClientError::Connection(anyhow::Error::new(value));
@@ -195,8 +201,6 @@ impl From<reqwest::Error> for HttpClientError {
                     .unwrap_or("Unknown URL".to_string()),
                 anyhow::Error::new(value),
             )
-        } else if value.is_timeout() {
-            HttpClientError::Timeout(anyhow::Error::new(value))
         } else if value.is_request() {
             HttpClientError::Request(anyhow::Error::new(value))
         } else {