-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing varnish configuration for API-Platform workflow #1824
Comments
Indeed, this docs entry needs to be updated. The VCL to use is here: https://github.com/api-platform/api-platform/blob/v2.1.6/docker/varnish/conf/default.vcl (cc @dbu). Also, we're in the process of integrating the Caddy Cache handler (which uses Souin) to replace Varnish: api-platform/api-platform#2383 |
Do you want me to create the PR or do you notify dbu so he change the entry?
I totally prefer this but changing existing nginx isn't a light task |
i do not plan to do a pull request for it, glad if you want to do it @vasilvestre and i just notice in the example that you invalidate tags with (the banlist needs to be checked against every request, and is a regex on the tags header. with xkey, varnish creates an optimized tree to look up keys so it can immediately invalidate the caches with those tags and avoid overhead) |
@dbu the part about xkey is documented in the documentation right ? Your point is that the vcl from dunglas don't handle this one case ? |
ah i did not look at the documentation. yeah that mentions xkey but the vcl needs to handle it as well. (and the doc could explain why xkey are preferred over ban) |
It's on my todolist to improve this but I'm stuck with website issues, feel free to propose a documentation for xkey. |
https://api-platform.com/docs/core/performance/#enabling-the-built-in-http-cache-invalidation-system does not contains any information about how APIP works with varnish.
This part in particular :
The text was updated successfully, but these errors were encountered: