Details
-
Bug
-
Resolution: Fixed
-
High
-
5.1, 5.2, 5.3-dev
-
None
-
ezp setup to environment "prod"
Description
the installation needs to be setup for prod, to have http caches fully working.
while the header Age: does not reach the s-maxage: the object is served from caches, even if it was removed in backend.
test case:
- create any object
- open the object in a frontend, non-legacy mode
- reload, to check that Age: is increasing
- in admin, remove object to trash
- in frontend, keep reloading
- object will be served until Age: >= s-maxage
Attachments
Issue Links
- links to