Bug #36022
Cache TER metadata in Varnish
| Status: | Closed | Start date: | 2012-04-14 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Tymoteusz Motylewski | % Done: | 0% |
|
| Category: | [Team] Server | |||
| Target version: | Code Sprint December | |||
| Votes: | 0 |
Description
We should cache those files in varnish:
/fileadmin/ter/extensions.md5
/fileadmin/ter/extensions.xml.gz
History
Updated by Steffen Gebert about 1 year ago
- Subject changed from Cache TER metadata to Cache TER metadata in Varnish
Updated by Tolleiv Nietsch 6 months ago
- Status changed from New to Accepted
Updated by Steffen Gebert 6 months ago
Maybe it isn't even a good idea.. What if a race condition occurs and (e.g.) old md5sum is delivered? We should have very short cache times nevertheless..
As I also plan to move TER to ter.typo3.org, maybe this task can be set to "on hold".
Updated by Joern Bock 6 months ago
- Target version set to Code Sprint December
Updated by Michael Stucki 6 months ago
- Assignee set to Tymoteusz Motylewski
Updated by Tymoteusz Motylewski 6 months ago
- Status changed from Accepted to Under Review
See gerrit https://review.typo3.org/#/c/17027/
Updated by Tymoteusz Motylewski 6 months ago
- Status changed from Under Review to Closed
deployed to production and tested