NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #4248 most downloaded on crates.io
Simple, minimal-dependency HTTP client
Latest stable
3.0.0
Last release 5 months ago
15 Jun 2026
Release timing varies
gaps range from 9 days to 7 months
Nearly every release is documented
notes for 45 of 46 stable releases
2 versions withdrawn
withdrawn after publishing
9 years old
52 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
This release includes many breaking changes as implied by the major version bump. See especially the Changed and Deleted sections below.
This changelog is identical to 3.0.0-rc.0, pasted here for convenience.
This release includes many breaking changes as implied by the major version bump. See especially the Changed and Deleted sections below.
This release includes all the planned changes that have been accumulating over the years for 3.0, renames some features, but otherwise tries to keep everything the same as 2.0.
minreq::Error type to be non-exhaustive, to make adding new errors later possible, and added new variants: NativeTlsCreateConnection, OpenSslCreateConnection, InvalidProtocol, and InvalidProtocolInRedirect.Response::headers and ResponseLazy::headers from HashMap<String, String> to Vec<(String, String)>, and removed lowercase normalization of the field names.
Response::header and Response::headers, to get the header value (or all values, if there are multiple of the same header) by field name. In other cases, iterate through and use str::eq_ignore_ascii_case to find your header(s).AsRef<str> instead of Into<String> to avoid unnecessary allocations. Thanks for the PR, @alpha-tango-kilo! (#69)Response::status_code and ResponseLazy::status_code type from i32 to u16. Thanks for the suggestion, @ModProg!
(#118)https-bundled to https-openssl, https-bundled-probe to https-openssl-probe, and https-native to https-native-tls to make them a little more obvious in what they bring in.Iterator impl for ResponseLazy, see the addition section for more on the new Read impl. Thanks for the PR, @mrkline! (#104)Response::header and Response::headers for ergonomically sorting through the headers of a response, now that they aren't in a convenient HashMap anymore.Read impl for ResponseLazy. This improves performance, and the Read trait generally matches the functionality better than Iterator. Thanks for the PR, @mrkline! (#104)Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing to see here, added some excludes in the Cargo.toml and cleaned up the rustls cert provider dependency feature gates. Just releasing these chan
Nothing to see here, added some excludes in the Cargo.toml and cleaned up the rustls cert provider dependency feature gates. Just releasing these changes as an RC so that the final RC would be identical to the actual 3.0.0 release.
Note that everything under Changed and Removed here is a breaking change.
This is the first release candidate for 3.0. If no issues are found, I'll release 3.0 in a few weeks.
Includes all the planned changes that have been accumulating over the years for 3.0, renames some features, but otherwise tries to keep everything the same as 2.0. Note that everything under Changed and Removed here is a breaking change.
minreq::Error type to be non-exhaustive, to make adding new errors later possible, and added new variants: NativeTlsCreateConnection, OpenSslCreateConnection, InvalidProtocol, and InvalidProtocolInRedirect.Response::headers and ResponseLazy::headers from HashMap<String, String> to Vec<(String, String)>, and removed lowercase normalization of the field names.
Response::header and Response::headers, to get the header value (or all values, if there are multiple of the same header) by field name. In other cases, iterate through and use str::eq_ignore_ascii_case to find your header(s).AsRef<str> instead of Into<String> to avoid unnecessary allocations. Thanks for the PR, @alpha-tango-kilo! (#69)Response::status_code and ResponseLazy::status_code type from i32 to u16. Thanks for the suggestion, @ModProg!
(#118)https-bundled to https-openssl, https-bundled-probe to https-openssl-probe, and https-native to https-native-tls to make them a little more obvious in what they bring in.Iterator impl for ResponseLazy, see the addition section for more on the new Read impl. Thanks for the PR, @mrkline! (#104)Response::header and Response::headers for ergonomically sorting through the headers of a response, now that they aren't in a convenient HashMap anymore.Read impl for ResponseLazy. This improves performance, and the Read trait generally matches the functionality better than Iterator. Thanks for the PR, @mrkline! (#104)Should be a pretty transparent update, pruning the log dependency for dependents which do not use it, and keeping everything the same for the ones tha
Should be a pretty transparent update, pruning the log dependency for dependents which do not use it, and keeping everything the same for the ones that do.
log crate optional. Thanks for the contribution, @Zodey-hub! (#122)Cleaned up the https-bundled and https-bundled-probe code quite a bit. Now it's more "openssl backend" rather than "native-tls backend but vendored",
Cleaned up the https-bundled and https-bundled-probe code quite a bit. Now it's more "openssl backend" rather than "native-tls backend but vendored", so the features might change their names to https-openssl in the next major version, whenever that ends up happening.
Also, added a new option for requests, Request::with_follow_redirects, which can be used to disable redirection, for cases where you want to read the redirection HTTP responses themselves.
https-bundled, https-bundled-probe: Removed almost all of the bundled native-tls code (~1k LoC), only keeping the relevant part (~30 LoC). There should be no change to the actual code that ends up being ran, but if you're using these features, make sure to test that everything works as you expect, something might have slipped.https-*: Refactored the TLS handling code a bit. This should have no visible effect downstream, src/connection.rs is just a little bit more readable now.build.rs, which turned out to be dead code. This should have no effect, but if it does, it should also only affect the https-bundled and https-bundled-probe features.Request::with_follow_redirects for disabling redirection handling. Thanks for the suggestion, @tachibanayui! (#120)Updated the base64 dependency, only used by the proxy feature, to its newest minor version. Thanks for the report, @Jackhr-arch!
proxy feature, to its newest minor version. Thanks for the report, @Jackhr-arch! (#119)A bit of dependency cleanup, and updated the list of crates that need to be pinned to build with MSRV.
A bit of dependency cleanup, and updated the list of crates that need to be pinned to build with MSRV.
once_cell dependency by making use of the new std::sync::OnceLock type. This change only affects the rustls-based https features. Thanks for the PR, @LyonSyonII! (#115)rustix update. Now tempfile is pinned as well."Cleaned up" some code in 2.13.1, thinking that minreq doesn't have a build.rs, but it does, and the code could actually be enabled via an environment
"Cleaned up" some code in 2.13.1, thinking that minreq doesn't have a build.rs, but it does, and the code could actually be enabled via an environment variable. Reverted that bit here.
Usage of an openssl-probe function that's deprecated due to safety issues. See rustsec/advisory-db#2209 for further info.
Only affects builds using the https-bundled-probe feature.
This is a tiny update to the copied-over native-tls cert loading code when using openssl-probe without native-tls, to avoid an apparently unsafe function in openssl-probe.
Small fixups all around, mostly code size improvements. In case your application depends specifically on webpki-roots certs being used, but still uses
Small fixups all around, mostly code size improvements. In case your application depends specifically on webpki-roots certs being used, but still uses the https-rustls-probe feature, I'm afraid you'll have to stay on 2.12. I hope this isn't the case for anyone.
Also: periodic MSRV CI did its job! It took me 5 days to notice the notification, but still a big improvement in issue-appearance-to-fix-latency.
https-rustls-probe feature no longer brings in the webpki-roots and rustls-webpki crates. Thanks for the report, @polarathene! (#111)format!() in Connection::connect. Thanks for the PR, @melotic! (#112)A new convenience function, Request::with_headers! And in maintenance news, I added a schedule for the msrv job, so hopefully I'll notice it failing w
A new convenience function, Request::with_headers! And in maintenance news, I added a schedule for the msrv job, so hopefully I'll notice it failing when it starts failing rather than on every new pull request.
Just a bump for a dev dependency. Unless your build process benefits from this, probably not too relevant.
Just a bump for a dev dependency. Unless your build process benefits from this, probably not too relevant.
Bugfixes and performance upgrades this time.
Nothing new in this version for those who don't care about the MSRV. For those who do, sorry, the crate no longer compiles out-of-the box with the new
Nothing new in this version for those who don't care about the MSRV. For those who do, sorry, the crate no longer compiles out-of-the box with the newest versions of dependencies that Cargo resolves, so you need to pin some version in your Cargo.lock a bit lower. Instructions in the readme!
serde_json, log and chrono dependencies (dev-dependency in the case of chrono). If you were depending on minreq compiling with the MSRV compiler without any issues, check out the MSRV section in the readme, it's been updated with additional instructions. Thanks for the report, @RCasatta! (#99)Three years into this major release, and I'm still finding new and exciting features of HTTP! Turns out, requests should *not* contain fragments, and
Three years into this major release, and I'm still finding new and exciting features of HTTP! Turns out, requests should not contain fragments, and the semantics about replacing fragments from the original url with the redirects' fragment are only relevant if the user agent wants to see the "final version" of the URL. Thus, minreq no longer sends the fragment in the request, and now responses have an url field.
Response::url and ResponseLazy::url fields, to contain the final URL after redirects and fragment replacement semantics.Loosened the rustls version requirement from 0.21.6 to 0.21.1.
Dependency cleanup release, including a few changes to examples and tests to get rid of serde_derive.
Dependency cleanup release, including a few changes to examples and tests to get rid of serde_derive.
>=1.0.0, <1.0.101)>=0.4.0, <0.4.19)>=0.4.0, <0.4.24)Turns out, proxies created including the http:// part haven't been working since the proxy feature was implemented. Also did a bit of a cleanup pass o
Turns out, proxies created including the http:// part haven't been working since the proxy feature was implemented. Also did a bit of a cleanup pass on the whole proxy module.
Default proxy from environment variables when the proxy feature is enabled, based on what curl does. Thanks for the PR, @krypt0nn!
proxy feature is enabled, based on what curl does. Thanks for the PR, @krypt0nn! (#94)Long time no release! This is a minor release thanks to the additions, explicitly the new Read impl for ResponseLazy, as well as --all-features now ac
Long time no release! This is a minor release thanks to the additions, explicitly the new Read impl for ResponseLazy, as well as --all-features now actually working. That said, I would not recommend enabling all features when using the library, you'll get a lot of unnecessary dependencies with it, thanks to the overlapping https features.
--all-features, with the send_https function defaulting to the rustls-based implementation. Thanks for the PR, @tcharding! (#89)First off, about the GitHub releases: every version between 2.0.1 and 2.6.0 seems to have been nuked, unfortunately. Sorry, if you were leaning on tho
First off, about the GitHub releases: every version between 2.0.1 and 2.6.0 seems to have been nuked, unfortunately. Sorry, if you were leaning on those. I accidentally removed the tags on github by pushing with --mirror from a version that did not have the tags. I managed to recover the tags, but GitHub seems to have misplaced the releases for the newer tags. Don't know why. The crates.io releases obviously still exist, and all the changes can be seen in the changelog.
Now, the actual 2.6.0. This time we have one new feature by @alpha-tango-kilo, urlencoding, which encodes any special characters in the url so that it can be properly handled by regular http servers. Previously, the idea was to leave the encoding up to the user, but as an optional feature, you can now avoid that manual work by using this feature. Overall internals improvements are included in this release as well.
https:// or http:// is now a slightly different IoError, with a clearer message. This will be changed to a proper minreq-specific error in 3.0, but for now it's an IoError to avoid breaking the Error type.Rustls updated from 0.19 to 0.20 and general cleanup.
Rustls updated from 0.19 to 0.20 and general cleanup.
Switched to Github Actions from Travis CI, and some fixes. Minor version bump because the "expected length" reported by ResponseLazy is now capped at
Switched to Github Actions from Travis CI, and some fixes. Minor version bump because the "expected length" reported by ResponseLazy is now capped at 16 KiB, so your code may behave differently. No API changes though. Next up: hopefully 3.0!
A regression in 2.4.1 where the port is no longer included in the Host, even if it's a non-standard port. Now the port is always included if it's in t
Host, even if it's a non-standard port. Now the port is always included if it's in the request URL, and omitted if the port is implied. Thanks for the report, @ollpu! (#61)The port is no longer included in the Host header when sending requests, and port handling was cleaned up overall. This fixes issues with infinite red
Host header when sending requests, and port handling was cleaned up overall. This fixes issues with infinite redirections and https handshakes for some websites. Thanks to @Shnatsel for reporting the issues, and @joeried for debugging and figuring out the root cause of these problems! (#48, #49)Request::with_param for more ergonomic query parameter usage. Thanks for the PR, @sjvignesh!
Request::with_param for more ergonomic query parameter usage. Thanks for the PR, @sjvignesh! (#54)Request::with_max_headers_size and Request::with_max_status_line_length for avoiding DoS when the server sends large headers or status lines. Thanks for the report, @Shnatsel! (#55)rustls-native-certs crate via a new https-rustls-probe feature. Thanks for the PR, @joeried! (#59)Removed some leftover printlns from the redirection update in 2.3.0 and ensured there's no printlns in the library anymore. Thanks for reporting the i
Breaking (sort of): the redirection code was improved to match RFC 7231 section 7.1.2, which could subtly break some programs relying on very specific
Location does not, the original fragment should be included in the new url. If Location does have a fragment, it should override the one in the redirecting url.Location is relative, e.g. /Foo.html instead of https://example.com/Foo.html. Thanks, @fjt523!Content-Length: 0 header is now inserted into requests that should have it. Thanks, @KarthikNedunchezhiyan!Documentation update. No code changes.
Documentation update. No code changes.
Support for native-tls and openssl-sys via new features, in addition to rustls. Thanks to @dubiousjim!
native-tls and openssl-sys via new features, in addition to rustls. Thanks to @dubiousjim!Handling of status codes 204 and 304. Thanks to @Mubelotix!
Proxy support via the proxy feature. Thanks to @rustysec!
proxy feature. Thanks to @rustysec!Accidentally broke header parsing in 2.0.2 for pretty much all cases that weren't broken before that. Didn't notice the regression before releasing be
Accidentally broke header parsing in 2.0.2 for pretty much all cases that weren't broken before that. Didn't notice the regression before releasing because I was running cargo test without --all-features. This version fixes that.
Some panics slipped by the unwrap-purification process, here's two of them fixed (reported in issues #23 and #24).
Some panics slipped by the unwrap-purification process, here's two of them fixed (reported in issues #23 and #24).
Made timeouts work as described in the documentation.
Fixed issue #22.
API for loading the HTTP response body through an iterator, allowing for processing of the data during the download.
The big API-breaking update.
ResponseLazy documentation for more information.? usage and better debuggability.punycode feature.hello, iterator, and json.response.headers.get("Content-Type"), you have to change it to response.headers.get("content-type"), or it will not return what you want.Response struct:
bytes and body_bytes.as_bytes(), into_bytes(), and as_str() in their place.with_body parameter type to Into<Vec<u8>> from Into<String>.
Strings implement Into<Vec<u8>>, so this shouldn't cause any problems, unless you're using some interesting types that implement Into<String> but not Into<Vec<u8>>.panic! when trying to make an https:// request without the https feature. The request will now return an error instead. The library should not panic anymore.unwrap()s from library code, none of them should actually ever cause a panic now.create_request in favor of just using Response::new.Nothing published for this version
Nothing published for this version
Tests on Windows by changing the ip in tests from 0.0.0.0 to localhost.
0.0.0.0 to
localhost.rustls::ClientConfig between requests.Content-Length and Transfer-Encoding detection failing because
of case-sensitiveness.This release provides json support in the form of a new feature that provides the capabilities to send and parse responses as json, via serde. Thanks
This release provides json support in the form of a new feature that provides the capabilities to send and parse responses as json, via serde. Thanks to @jonas-l for the whole feature!
json-using-serde feature, PR #15.Switched to handling HTTP responses as byte vecs instead of strings, so now you can download images and other non-UTF-8 content.
Switched to handling HTTP responses as byte vecs instead of strings, so now you can download images and other non-UTF-8 content.
body_bytes field to Response, which contains the body in raw bytes.body to just an empty string. The aforementioned body_bytes will still contain the actual body.body_bytes field to Response, containing the body in raw
bytes.body
string to an empty string, for now.Previously, the http response was split into lines, and then the body was manually reconstructed from the lines, with \r\n between. This obviously doe
Previously, the http response was split into lines, and then the body was manually reconstructed from the lines, with \r\n between. This obviously doesn't preserve the original body very well. This is now fixed, and the body should be exactly as the sender wrote it. Thanks @shanavas786 for the code review!
Added redirection support. Covering more and more of the http standard by the month! In addition, this release includes memory optimizations by @gnuvi
Added redirection support. Covering more and more of the http standard by the month! In addition, this release includes memory optimizations by @gnuvince, thanks for the contribution!
Finally fixed a long-standing bug regarding chunked encoding. Thanks to @iamcharleschege for troubleshooting and figuring out the problem!
Finally fixed a long-standing bug regarding chunked encoding. Thanks to @iamcharleschege for troubleshooting and figuring out the problem!
Transfer-Encoding header's value is chunked.Miscellaneous cleanup, 2018 edition, and a bug fix. Thanks to @mattgathu for the contributions!
Miscellaneous cleanup, 2018 edition, and a bug fix. Thanks to @mattgathu for the contributions!
First patch with features from outside contributors! Alas, these PR's could've been merged before 1.0.3, so almost a year ago, but I didn't notice I h
First patch with features from outside contributors! Alas, these PR's could've been merged before 1.0.3, so almost a year ago, but I didn't notice I had PRs lying around. That said, a late thanks to @gnuvince for the contributions, and here's the changes.
Nothing published for this version
Nothing published for this version
Fix weird behaviour explained in 246a8a080fdfd298908c80558516b936b33a8f64
Reasons. This is the real 1.0.0 though.
Reasons. This is the real 1.0.0 though.
Removed a broken test, this is functionally the same as 0.1.1
You can do basic HTTP requests with bodies and headers.
One column per quarter.