From 521e8efb43c8d54e5d226a0b008ae0b6a5a110d6 Mon Sep 17 00:00:00 2001 From: David Buchmann Date: Tue, 10 Oct 2023 08:37:13 +0200 Subject: [PATCH] fix bullet lists in doc --- Resources/doc/reference/configuration/proxy-client.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Resources/doc/reference/configuration/proxy-client.rst b/Resources/doc/reference/configuration/proxy-client.rst index d9d909ab..9ea40480 100644 --- a/Resources/doc/reference/configuration/proxy-client.rst +++ b/Resources/doc/reference/configuration/proxy-client.rst @@ -88,6 +88,7 @@ Use this option only when using a variable amount of proxy servers that shall be environment variable. Otherwise use the regular ``http.servers`` option. Usage: + * ``fos_http_cache.yaml``: ``servers_from_jsonenv: '%env(json:VARNISH_SERVERS)%'`` * environment definition: ``VARNISH_SERVERS='["123.123.123.1:6060","123.123.123.2"]'`` @@ -151,8 +152,9 @@ default ``xkey-softpurge``. Header for sending tag invalidation requests to Varnish. For use with ``tag_mode: purgekeys``, default VCL supports two options: -- ``xkey-softpurge``: "Soft purge" by tags, expires relevant cache and allows for grace handling. -- ``xkey-purge``: Purge by tags, removes relevant cache immediately. + +* ``xkey-softpurge``: "Soft purge" by tags, expires relevant cache and allows for grace handling. +* ``xkey-purge``: Purge by tags, removes relevant cache immediately. See the :ref:`FOSHttpCache library docs ` on how to configure Varnish to handle tag invalidation requests.