Skip to content

Commit 5cc67f6

Browse files
authored
Update README.md
1 parent 9e4898c commit 5cc67f6

1 file changed

Lines changed: 26 additions & 1 deletion

File tree

README.md

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,29 @@
11
Full Page Cache
22
===============
33

4-
Still WIP but cache invalidation should work just fine and this package should bring performance improvements without drawback (apart from having more caches to store) for many websites. Next steps would be proxy cache headers and better ways to influence the caching from within the request.
4+
This package is meant to cache full HTTP responses for super fast delivery time. It currently works with Neos but a plan is there to provide the functionality for Flow as well.
5+
6+
It works by checking if a page is fully cachable and in that case caching the whole HTTP response and delivering it immediately. So this won't have much effect on websites with uncached elements on every page. Also POST requests and requests with query arguments are excluded from caching, as well as requests that set cookies. So if you don't see a difference after installing, these are things to look out for.
7+
8+
Settings
9+
--------
10+
11+
Two settings are available to you to influence the behavior.
12+
13+
```
14+
Flowpack:
15+
FullPageCache:
16+
# enable full page caching
17+
enabled: true
18+
19+
# the maximum public cache control header sent
20+
# set to 0 if you do not want to send public CacheControl headers
21+
maxPublicCacheTime: 86400
22+
```
23+
24+
You can also move the cache backend to something faster if available, to improve performance even more.
25+
26+
Warning
27+
-------
28+
29+
This package is still fairly new, if you install it, make sure to check really well if your page still works. Especially things like Forms and plugins. Ideally those pages should work but just not be faster unlike pure content pages. Still this was tested in limited scenarios so far, so make sure you tested properly before bringing this to production. It has no effect on the content itself, so deinstalling it will bring you back to the state you had before.

0 commit comments

Comments
 (0)