Repository navigation
docs: add the reverse proxy cache guide - #85
Merged
Merged
Conversation
…hat keep a page personal
…odule declare what it shares
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a page to the getting started section, "Reverse proxy cache", for the shared cache of thelia/thelia#4148 (Thelia 3.3). It is only in the next version of the docs, since the feature is not released.
The page covers the two settings, what is shared and what is not, the keys a page carries, what purges what, the environment variables of the purge, a Varnish configuration for the
enabledmode and another forannounce, how to check that it works, what is not purged and the limits. A warning explains why a proxy must drop the forwarded headers a visitor sent, and another whyannounceis only safe with a proxy that removes the session cookie.The Varnish configurations were run against Varnish 7.6 with a stub backend: hit and miss, requests with a cookie, a
PURGEby key, the refusal of a purge without the secret, and the removal ofX-Forwarded-PrefixandForwarded. Souin was tried as the standalone image: it stores and serves the pages with their keys, but its purge was not demonstrated, and the page says so. The generic surrogate key purger was not tried against a proxy. The page also names two things that keep a page personal: a module that reads a resource outside the list (HeaderHighlights on the demo) and the filter form of a category, whose Flexy fix is in thelia-templates/flexy#288.The "Application cache" page now links to the new one in place of saying that the HTTP cache is configured only on the proxy.
npm run buildpasses; it reports three broken anchors in pages of version 2.x that this PR does not touch.