Could you explain why you changed how the features work?

Because I misread the new features and thought only rustls was available, I'll fix this.

I wonder if the "default-tls" feature should be renamed to "native-tls", and maybe the default switched to rustls, as the default for both ureq and reqwest is rustls.
As a side note, i686-apple-darwin support in rustc was changed from tier1 to tier3 in Rust 1.42.0, and it was six years ago.

Because I misread the new features and thought only rustls was available, I'll fix this.

Looks good now, thanks!

I wonder if the "default-tls" feature should be renamed to "native-tls", and maybe the default switched to rustls, as the default for both ureq and reqwest is rustls.

Probably, feel free to open an issue. (but I'm not going to deal with that right now)

As a side note, i686-apple-darwin support in rustc was changed from tier1 to tier3 in Rust 1.42.0, and it was six years ago.

Sorry what do you mean by this? Is this related to the reqwest update?

As a side note, i686-apple-darwin support in rustc was changed from tier1 to tier3 in Rust 1.42.0, and it was six years ago.

Sorry what do you mean by this? Is this related to the reqwest update?

This is about the README file that says:

rustls: Use pure rust TLS implementation for network requests. This feature does not support 32bit macOS;