Open bruceg opened 12 months ago
Seems like https://crates.io/crates/http-types and https://crates.io/crates/hyper-proxy are on the latest version.
Also, https://crates.io/crates/tokio-tungstenite (PR) is another crate that seems to affected by the http upgrade.
Yes, both http-types
and hyper-proxy
do not have a released version that upgrades their usage to http
1.0. So, we are using their latest versions, but upgrading the other crates without those breaks the build.
Agreed, at least part of the tokio-tungstenite
breakage is caused by this issue. I'll add that to the list.
Note that hyper-proxy
appears to be unmaintained, as the last commit was 3 years ago, which may require converting Vector to use hyper-proxy2
(link) or handling proxying manually.
Similarly, the last commit to http-types
was 2 years ago, but replacing it will be more difficult as it is depended on by azure_core
and wiremock
.
tonic
now has released an updated version for the http
/hyper
1.0 upgrade.
https://github.com/hyperium/tonic/blob/master/CHANGELOG.md
That just leaves the two unmaintained crates, which will need to either be removed or forked and handled ourselves.
This requires updating several crates simultaneously, only some of which currently have updates to their
http
dependencies. I will update this issue as the dependency crates are bumped:azure-sdk-for-rust
https://github.com/Azure/azure-sdk-for-rust/issues/1644axum
v0.7.0h2
v0.4.0headers
v0.4.0http
v1.0.0http-body
v1.0.0http-serde
v2.0.0http-types
https://github.com/http-rs/http-types/issues/520hyper
v1.0.1hyper-openssl
v0.10.1hyper-proxy
https://github.com/tafia/hyper-proxy/issues/42tonic
v0.12.0tower-http
v0.5.0