Skip to content

Commit 383092a

Browse files
committed
tweak changelog
1 parent f538e2b commit 383092a

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

CHANGELOG.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,23 +3,23 @@ Changelog
33

44
See also the [GitHub releases page](https://github.com/FriendsOfSymfony/FOSHttpCache/releases).
55

6-
2.16
7-
----
6+
2.16.0
7+
------
88

99
### Symfony HttpCache
1010

1111
* Add events `PRE_FORWARD` and `POST_FORWARD` to allow event listeners to alter
1212
the request before and after it is sent to the backend.
1313
* Changed CustomTtlListener to use the `POST_FORWARD` event instead of
14-
`PRE_STORE`. Using PRE_STORE, requests that are not considered cacheable by
14+
`PRE_STORE`. Using `PRE_STORE`, requests that are not considered cacheable by
1515
Symfony were never cached, even when they had a custom TTL header.
1616
* Add flag `fallbackToSmaxage` to `CustomTtlListener` to allow controlling
17-
fallback to s-maxage if custom TTL header is not defined on the response.
17+
fallback to `s-maxage` if custom TTL header is not defined on the response.
1818
* Fix: Do not call store if Response object is not longer cacheable after event
1919
listeners. If you use the custom TTL system, this is only a performance
2020
improvement, because the TTL of the response would still be 0. With a custom
2121
listener that changes the response explicitly to not be cached but does not
22-
change s-maxage, this bug might have led to caching responses that should not
22+
change `s-maxage`, this bug might have led to caching responses that should not
2323
have been cached.
2424

2525
2.15.3

0 commit comments

Comments
 (0)