Releases: imbolc/tower-cookies
Axum-0.7, Cookie-0.18
Update to cookie 0.17
Breaking change because cookie is part of the public API.
What's Changed
- Update to cookie 0.17 by @davidpdrsn in #26
Full Changelog: v0.8.1...v0.9.0
`cookie` crate re-export
What's Changed
- Github actions by @imbolc in #21
- Change private jar docs to reflect that they are also signed by @sweepline in #22
- feat: add cookie re-export by @alexschrod in #24
New Contributors
- @sweepline made their first contribution in #22
- @alexschrod made their first contribution in #24
Full Changelog: v0.8.0...v0.8.1
Updated for Axum 0.6
Thank you @fasterthanlime π
Static lifetimes in signed / private cookies
Before this commit, the Key
that's passed to Cookies::signed()
or Cookies::private()
is forced to have a static lifetime, because the returned Cookie
gets self's lifetime as its lifetime parameter. Now the Cookie
gets static lifetime instead.
This makes it possible e.g. to store Key
in an axum Extension layer instead of a global Cell.
Thank you @akheron π
Updated for Axum 0.5
Thank you, @genusistimelord π
Http2 compatibility
Added support for HTTP2 multiple Cookie headers: https://www.rfc-editor.org/rfc/rfc7540#section-8.1.2.5
Thank you @charlesdaniel π
Upgrade dependencies to their latest versions
The following deps were upgraded:
- cookie: updated to 0.16. it is important to note that this is a breaking
change because the MSRV is 1.53. This is also an important update since it
bumps the transitive dependencytime
to 0.3 which includes a multitude of
fixes and improvements - parking_lot: updated to 0.12. This is also a breaking change that increases
the MSRV to 1.49
Thank you @ohsayan π
Private cookies
async fn handler(cookies: Cookies) -> String {
cookies.private(&my_key).get("my_cookie").unwrap().value.into()
}
Thank you @zvkemp π
Update to axum-core 0.1
This changes tower-cookies
to have a public dependency on axum-core
instead of axum
.
axum-core
is designed to be a small crate that only contains the
FromRequest
and IntoResponse
traits. Because of the smaller API its
less likely to receive breaking changes. Therefore its recommended for
library to depend on that instead of axum
.
Note this is a breaking change since axum
0.3 doesn't know about
axum-core
.
Thank you @davidpdrsn π