Bump http-types from 2.9.0 to 2.11.0

[dependabot-preview]

Bumps http-types from 2.9.0 to 2.11.0.

Release notes

Sourced from http-types's releases.

v2.11.0

http-types provides shared types for HTTP operations. It combines a performant, streaming interface with convenient methods for creating headers, urls, and other standard HTTP types. This is part of the http-rs project and powers the tide framework and surf client. Check out the docs or join us on Zulip.

Highlights

This release represents continued support of the http-types 2.x release line due to delays in the development of http-types 3.0.0. This release comes with several convenience features, listed below.

The http-types 3.0 merge window remains open, and you can see the nominated items for the next major version as part of the Semver-Major issue on GitHub.

Changed

• Allowed Request.query() to deserialize into a borrowed Deserialize<'de> rather than just DeserializeOwned. #333
  • This is a looser restriction and is not a breaking change. See serde's documentation on the subject.

Added

• More HTTP Methods from the IANA registry. #332
• Body::chain() for merge multiple Body instances. #342, #346
• AsRef<str> for Version, returning 'static str. #351
• Error::from_debug(), a helper for converting from std::error::Errors. #345
• Error::from_display, a helper for converting from std::error::Errors. #345

Fixed

• Corrected error messages for Content-Encoding and Transfer-Encoding. #354

Docs

• Improved request examples with the url's crate new TryFrom<&str>. #324
• 4xx status codes now have the right descriptions. #341
• Fixed for Content-Encoding and Transfer-Encoding docs. #354

v2.10.0

http-types provides shared types for HTTP operations. It combines a performant, streaming interface with convenient methods for creating headers, urls, and other standard HTTP types. This is part of the http-rs project and powers the tide and surf frameworks. Check out the docs or join us on Zulip.

Highlights

This release introduces several new typed headers:

• transfer::TransferEncoding: The form of encoding used to safely transfer the payload body to the user.
• transfer::TE: Client header advertising the transfer encodings the user agent is willing to accept.
• other::RetryAfter: Indicate how long the user agent should wait before making a follow-up request.
• other::Referer: Contains the address of the page making the request.
• content::Accept: Client header advertising which media types the client is able to understand.
• content::ContentType: Indicate the media type of a resource's content.

Most notably is probably the RetryAfter header, which can be used to enable load-shedding on the client. An example of such a middleware has been authored for Tide.

http-types 3.0 merge window opened

This marks the final release of the 2.x release line of http-types. It's been almost a year since our last major release, and we've decided to open up the merge window for http-types 3.0 now that 2.10.0 has shipped. You can see the nominated items for the next major version as part of the Semver-Major issue on GitHub.

Because this is the first major release of http-types we're doing since we moved to our monthly release cadence, we're not entirely sure yet how we'll manage this. Perhaps next month's release may be a beta release. Or we may delay doing a release at all until all items have been merged. We'll have to see, but once 3.0 is out we'll resume the monthly release cadence.

... (truncated)

Commits

• dc6367c 2.11.0
• 7c1b74f Fixes error messages in Content-Type and Transfer-Encoding negotiation
• b3fa1db chore: fix new clippy lints v2.x
• 5c7c02e chore: cargo fmt --all
• 925e4a8 feat: add Error::from_display & from_debug
• 125f72b feat: add AsRef<str> for Version
• 65f5c41 Request: allow Deserialize<'de> for .query()
• c49051d Make Body::chain not depend on the async-std feature
• 339b633 Add a test for Body::chain on Body instances after calling read
• bcde50c Add Body::chain to create a Body from a series of two Body instances
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #32.