tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 12:05:37 +00:00
Code Issues Projects Releases Wiki Activity

List deprecated APIs in changelog

Browse Source
This commit is contained in:
Ingo Schommer 2018-06-14 13:31:25 +12:00
parent 4c30c9ac2f
commit 3625b2553d
2 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/02_Developer_Guides/08_Performance/02_HTTP_Cache_Headers.md
View File

@ -21,8 +21,8 @@ are a great way to learn about HTTP caching.
In order to support developers in making safe choices around HTTP caching,
we're using a `HTTPCacheControlMiddleware` class to control if a response
should be considered public or private. This is an abstraction on existing
lowlevel APIs like `HTTP::add_cache_headers()` and `HTTPResponse->addHeader()`.
should be considered public or private. This is an abstraction on the
`HTTPResponse->addHeader()` lowlevel API.
The `HTTPCacheControlMiddleware` API makes it easier to express your caching preferences
without running the risk of overriding essential core safety measures.

17
docs/en/04_Changelogs/4.2.0.md
View File

@ -207,9 +207,9 @@ SilverStripe\Core\Injector\Injector:
#### Overview
In order to support developers in making safe choices around HTTP caching,
we've introduced a `HTTPCacheControlMiddleware` class to control if a response
should be considered public or private. This is an abstraction on existing
lowlevel APIs like `HTTP::add_cache_headers()` and `HTTPResponse->addHeader()`.
we're using a `HTTPCacheControlMiddleware` class to control if a response
should be considered public or private. This is an abstraction on the
`HTTPResponse->addHeader()` lowlevel API.
This change introduces smaller but necessary changes to HTTP caching headers
sent by SilverStripe. If you are relying on HTTP caching in your implementation,
@ -344,7 +344,7 @@ class PageController extends ContentController
}
```
#### Detailed Cache-Control Changes:
#### Detailed Cache-Control Changes
* Added `Cache-Control: no-store` header to default responses,
to prevent intermediary HTTP proxies (e.g. CDNs) from caching unless developers opt-in
@ -360,4 +360,11 @@ class PageController extends ContentController
* DataObject no longer automatically invokes `HTTP::register_modification_date`
with LastModified on construction. User code should instead invoke
`HTTPCacheControlMiddleware::singleton()->registerModificationDate()` explicitly.
* Deprecated `HTTP::add_cache_headers()`. Headers are added automatically by `HTTPCacheControlMiddleware` instead.
* Deprecated `HTTP::set_cache_age()`. Use `HTTPCacheControlMiddleware::singleton()->setMaxAge($age)`
* Deprecated `HTTP.cache_ajax_requests`. Use `HTTPCacheControlMiddleware::disableCache()` instead
* Deprecated `HTTP.modification_date`. Handled by `HTTPCacheControlMiddleware`
* Deprecated `HTTP.disable_http_cache`. Use `HTTPCacheControlMiddleware.defaultState` and `defaultForcingLevel` instead
* Deprecated `HTTP::register_modification_date()`. Use `HTTPCacheControlMiddleware::registerModificationDate()` instead
* Deprecated `HTTP::register_modification_timestamp()`. Use `HTTPCacheControlMiddleware::registerModificationDate()` instead
* Deprecated `HTTP::register_etag()`. Use `HTTPCacheControlMiddleware::ETagMiddleware()` instead