how to get response text in error handling (3.0.x)?

[tessus]

Error handling has changed in 3.0.x and the response is no longer part of the error.

So how are we supposed to print the response from the server in case of an error?
We've been using the following code in the error branch:

Err(UreqError::Status(code, response)) => Err(Error::UploadError(format!(
                "{} (status code: {})",
                response.into_string()?.trim(),
                code
            ))),

Link to full code: https://github.com/orhun/rustypaste-cli/blob/master/src/upload.rs#L205-L209

[algesten]

I believe this is answered in this comment. #997 (comment)

Let me know if that helps.

[tessus]

Thanks for the info. I guess a more elaborate rewrite is necessary. ;-)

The fact that there is no native multipart support in ureq might unfortunately force us to use somthing else altogether, because the available multipart crates are either unmaintained or broken.

[algesten]

The fact that there is no native multipart support in ureq might unfortunately force us to use somthing else altogether, because the available multipart crates are either unmaintained or broken.

Oh, ok. I haven't been looking at that for a while. If there isn't a good solve, I'd be open to add support for it in ureq.

[tessus]

If there isn't a good solve

If there is, we haven't found it. We are open to suggestions. ;-)

The crates that can be used are multipart and ureq_multipart, the former is unmaintained and the second one hasn't reeived an update for over a year.
Now with major changes in ureq 3, I do not even know whether the multipart crate will still work. Apart from the fact that we get security notices all the time that multipart is unmaintained.
Either way, we have to figure out what to do. The rustypaste-cli dev chose ureq, because it had a very small footprint and was easy to use. It also doesn't pull in a myriad of dependencies as other clients do, which is also a huge plus.

But the changes in v3 made a few things more complicated. e.g. previously we only had to use the feature native-certs so that the root certs of the OS are used. With v3, we have to add the feature platform-verifier and make additional code changes (when creating the agent), which is a bit messy with #[cfg(feature = "use-native-certs")] directives.