diff options
| author | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2019-01-02 17:11:59 +0900 |
|---|---|---|
| committer | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2019-01-07 07:52:29 +0900 |
| commit | c1dd2285799b19b7067119b2aa121ca922b75bc3 (patch) | |
| tree | ad491f578c133dc443b549a91c21373eb82ecc3a /railties/test | |
| parent | 1e09019088760adafaa122eb11c24effdb4c1160 (diff) | |
| download | rails-c1dd2285799b19b7067119b2aa121ca922b75bc3.tar.gz rails-c1dd2285799b19b7067119b2aa121ca922b75bc3.tar.bz2 rails-c1dd2285799b19b7067119b2aa121ca922b75bc3.zip | |
Allow using combine the Cache-Control `public` and `no-cache` headers
Since #30367, if `no-cache` includes Cache-Control headers, special keys
like `public`, `must-revalidate` are ignored.
But in my understanding, `public` still need in case of want to cache
authenticated pages.
The authenticated pages to be cacheable, but still authenticated for
every user, need to specify the `Cache-Control: public, no-cache`.
For keys other than `public`, I did not know the case where it was
necessary to use it in combination with `no-cache`, so I fixed that can
be used only for `public`.
Ref: https://www.mnot.net/cache_docs/#CACHE-CONTROL
Fixes #34780.
Diffstat (limited to 'railties/test')
0 files changed, 0 insertions, 0 deletions