Skip to content

Commit

Permalink
Release 0.3.0 (#252)
Browse files Browse the repository at this point in the history
  • Loading branch information
davidpdrsn authored Apr 25, 2022
1 parent 0c68c06 commit 1f111cc
Show file tree
Hide file tree
Showing 2 changed files with 34 additions and 15 deletions.
47 changes: 33 additions & 14 deletions tower-http/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,38 +9,57 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## Added

- Add `ServeDir::{fallback, not_found_service}` for calling another service if
the file cannot be found.
- Add `SetStatus` to override status codes.
- None.

## Changed

- None.

## Removed

- None.

## Fixed

- None.

# 0.3.0 (April 25, 2022)

## Added

- **fs**: Add `ServeDir::{fallback, not_found_service}` for calling another service if
the file cannot be found ([#243])
- **fs**: Add `SetStatus` to override status codes ([#248])
- `ServeDir` and `ServeFile` now respond with `405 Method Not Allowed` to requests where the
method isn't `GET` or `HEAD`.
method isn't `GET` or `HEAD` ([#249])
- **cors**: Added `CorsLayer::very_permissive` which is like
`CorsLayer::permissive` except it (truly) allows credentials. This is made
possible by mirroring the request's origin as well as method and headers
back as CORS-whitelisted ones
- **cors**: Allow customizing the value(s) for the `Vary` header
back as CORS-whitelisted ones ([#237])
- **cors**: Allow customizing the value(s) for the `Vary` header ([#237])

## Changed

- **cors**: Removed `allow-credentials: true` from `CorsLayer::permissive`.
It never actually took effect in compliant browsers because it is mutually
exclusive with the `*` wildcard (`Any`) on origins, methods and headers
exclusive with the `*` wildcard (`Any`) on origins, methods and headers ([#237])
- **cors**: Rewrote the CORS middleware. Almost all existing usage patterns
will continue to work. (BREAKING)
will continue to work. (BREAKING) ([#237])
- **cors**: The CORS middleware will now panic if you try to use `Any` in
combination with `.allow_credentials(true)`. This configuration worked
before, but resulted in browsers ignoring the `allow-credentials` header,
which defeats the purpose of setting it and can be very annoying to debug.

## Removed

- None.
which defeats the purpose of setting it and can be very annoying to debug
([#237])

## Fixed

- Fix content-length calculation on range requests ([#228])
- **fs**: Fix content-length calculation on range requests ([#228])

[#228]: https://github.com/tower-rs/tower-http/pull/228
[#237]: https://github.com/tower-rs/tower-http/pull/237
[#243]: https://github.com/tower-rs/tower-http/pull/243
[#248]: https://github.com/tower-rs/tower-http/pull/248
[#249]: https://github.com/tower-rs/tower-http/pull/249

# 0.2.4 (March 5, 2022)

Expand Down
2 changes: 1 addition & 1 deletion tower-http/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
name = "tower-http"
description = "Tower middleware and utilities for HTTP clients and servers"
version = "0.2.3"
version = "0.3.0"
authors = ["Tower Maintainers <team@tower-rs.com>"]
edition = "2018"
license = "MIT"
Expand Down

0 comments on commit 1f111cc

Please sign in to comment.