docs/guide/cache/*.md: Fix links

Author: adriendupuis

docs/guide/cache/content_aware_cache.md

@@ -92,7 +92,7 @@ Apache has a [hard](https://github.com/apache/httpd/blob/5f32ea94af5f1e7ea68d6fc
 1\. For inline rendering just displaying the content name, image attribute, and/or link, it would be enough to:
 
 - Look into how many inline (non ESI) render calls for content rendering you are doing, and see if you can organize it differently.
-- Consider inlining the views not used elsewhere in the given template and [tagging the response in Twig](#response-tagging-in-twig) with "relation" tags.
+- Consider inlining the views not used elsewhere in the given template and [tagging the response in Twig](#response-tagging-in-templates) with "relation" tags.
     - (Optional) You can set reduced cache TTL for the given view, to reduce the risk of stale cache on subtree operations affecting the inlined content.
 
 2\. You can opt in to set a max length parameter (in bytes) and corresponding ttl (in seconds) 
@@ -197,7 +197,7 @@ but parent response needs these tags to get refreshed if they are deleted:
 $responseTagger->addTags([ContentTagInterface::RELATION_PREFIX . '33', ContentTagInterface::RELATION_PREFIX . '34']);
 ```
 
-See [Tagging from code](https://foshttpcachebundle.readthedocs.io/en/2.8.0/features/tagging.html#tagging-and-invalidating-from-php-code) in FOSHttpCacheBundle doc.
+See [Tagging from code](https://foshttpcachebundle.readthedocs.io/en/stable/features/tagging.html#tagging-and-invalidating-from-php-code) in FOSHttpCacheBundle doc.
 
 4\. Use deprecated `X-Location-Id` header.
 
@@ -250,7 +250,7 @@ As a last resort you can also use the following function from FOS which lets you
 {{ fos_httpcache_tag(['r33', 'r44']) }}
 ```
 
-See [Tagging from Twig Templates](https://foshttpcachebundle.readthedocs.io/en/latest/features/tagging.html#tagging-from-twig-templates) in FOSHttpCacheBundle documentation.
+See [Tagging from Twig Templates](https://foshttpcachebundle.readthedocs.io/en/stable/features/tagging.html#tagging-from-twig-templates) in FOSHttpCacheBundle documentation.
 
 ## Tag purging
 
@@ -400,7 +400,7 @@ To find a valid route, click an element in the **URLs** drop-down for the specif
 A route may look like this:
 `https://www.staging.foobar.com.us-2.platformsh.site/`
 
-In this case the region is `us-2` and you can find the public IP list on [Platform.sh documentation page](https://docs.platform.sh/development/public-ips.html)
+In this case the region is `us-2` and you can find the public IP list on [Platform.sh documentation page](https://docs.platform.sh/development/regions.html#public-ip-addresses)
 Typically, you can add a `gw` to the hostname and use nslookup to find it.
 
 ```bash

docs/guide/cache/context_aware_cache.md

@@ -18,7 +18,7 @@ A similar but internal logic is done in the provided enhanced Symfony Proxy (App
 
 ## Request lifecycle
 
-This expands steps covered in [FOSHttpCacheBundle documentation on user context feature](https://foshttpcachebundle.readthedocs.io/en/latest/features/user-context.html#how-it-works):
+This expands steps covered in [FOSHttpCacheBundle documentation on user context feature](https://foshttpcachebundle.readthedocs.io/en/stable/features/user-context.html#how-it-works):
 
 1. A client (browser) requests URI `/foo`.
 1. The caching proxy receives the request and holds it. It first sends a hash request to the application's context hash route: `/_fos_user_context_hash`.
@@ -32,7 +32,7 @@ as the hash lookup itself is cached by the cache proxy as described below.
 
 ### User context hash caching
 
-Example of a response sent to reverse proxy from `/_fos_user_context_hash` with [[[= product_name =]]'s default config](#default-options-for-FOSHttpCacheBundle-defined-in-ibexa-dxp):
+Example of a response sent to reverse proxy from `/_fos_user_context_hash` with [[[= product_name =]]'s default config](#default-options-for-foshttpcachebundle):
 
 ```
 HTTP/1.1 200 OK
@@ -68,6 +68,7 @@ It also varies on `Authorization` to cover any possible basic authorization head
 
 !!! caution "Default options for FOSHttpCacheBundle"
 
+    <a name="default-options-for-foshttpcachebundle"></a>
     The following configuration is defined by default for FOSHttpCacheBundle.
     You should not override these settings unless you know what you are doing.
 
@@ -125,16 +126,16 @@ This solution requires more effort (controller, VCL logic and adapting your own
     If you need to handle a paywall on a per-item basis, or example, do a
     lookup to backend for each URL where this is relevant.
 
-    You can find an example for paywall authorization in [FOSHTTPCache documentation.](https://foshttpcache.readthedocs.io/en/latest/user-context.html#alternative-for-paywalls-authorization-request)
+    You can find an example for paywall authorization in [FOSHTTPCache documentation.](https://foshttpcache.readthedocs.io/en/stable/user-context.html#alternative-for-paywalls-authorization-request)
 
 ### Best practices for custom vary by logic
 
-For information on how user context hashes are generated, see [FOSHttpCacheBundle documentation](https://foshttpcachebundle.readthedocs.io/en/latest/features/user-context.html#generating-hashes).
+For information on how user context hashes are generated, see [FOSHttpCacheBundle documentation](https://foshttpcachebundle.readthedocs.io/en/stable/features/user-context.html#generating-hashes).
 
 [[= product_name =]] implements a custom context provider in order to make user context hash reflect the current User's Roles and Limitations.
 This is needed given [[= product_name =]]'s more complex permission model compared to Symfony's.
 
-You can technically extend the user context hash by [implementing your own custom context provider(s)](https://foshttpcachebundle.readthedocs.io/en/latest/reference/configuration/user-context.html#custom-context-providers).
+You can technically extend the user context hash by [implementing your own custom context provider(s)](https://foshttpcachebundle.readthedocs.io/en/stable/reference/configuration/user-context.html#custom-context-providers).
 However, **this is strongly discouraged** as it means increasing the amount of cache variations
 stored in proxy for every single cache item, lowering cache hit ratio and increasing memory use.
 
@@ -151,7 +152,7 @@ needs, and adapt the user context hash VCL logic to use the additional header.
 
 To avoid overloading any application code, take advantage of Symfony's event system:
 
-1\. Add a [Response event (`kernel.response`)](https://symfony.com/doc/5.4/reference/events.html#kernel-response) [listener or subscriber](https://symfony.com/doc/5.4/event_dispatcher.html) to add your own hash to `/_fos_user_context_hash`:
+1\. Add a [Response event (`kernel.response`)]([[= symfony_doc =]]/reference/events.html#kernel-response) [listener or subscriber]([[= symfony_doc =]]/event_dispatcher.html) to add your own hash to `/_fos_user_context_hash`:
 
 ```php
 public function addPreferenceHash(FilterResponseEvent $event)

docs/guide/cache/fastly.md

@@ -5,7 +5,7 @@ description: Configure Fastly for use with Ibexa DXP.
 # Configure and customize Fastly
 
 You can configure Fastly by using API calls or through the Fastly Web Interface. 
-Fastly provides a [Fastly CLI](https://developer.fastly.com/reference/cli/) for configuring Fastly through its API.
+Fastly provides a [Fastly CLI](https://www.fastly.com/documentation/reference/cli/) for configuring Fastly through its API.
 
 Ibexa Cloud is delivered with Fastly preconfigured. 
 It means that you don't have to do any changes to the Fastly configuration to make your site work. 
@@ -44,7 +44,7 @@ When you configure the Fastly CLI, use the credentials for the environment that
 
 Use the commands below to install VCL configuration required for running Fastly with [[= product_name =]].
 You also need to set up domains, HTTPS and origin configuration (not covered here).
-All commands are explained in detail [below](#viewing-and-modifying-the-vcl-configuration):
+All commands are explained in detail [below](#view-and-modify-vcl-configuration):
 
 ``` bash
 fastly vcl custom create --name=ez_main.vcl --version=active --autoclone --content=vendor/ezsystems/ezplatform-http-cache-fastly/fastly/ez_main.vcl --main
@@ -335,11 +335,11 @@ diff -ruN generated_vcl_11_json_done generated_vcl_12_json_done
 
 ## Enable basic-auth on Fastly
 
-To enable basic-auth, use [Fastly documentation](https://developer.fastly.com/solutions/examples/http-basic-auth) as an example.
+To enable basic-auth, use [Fastly documentation](https://www.fastly.com/documentation/solutions/examples/http-basic-auth/) as an example.
 
 Follow the steps below.
 
-Usernames and passwords can be stored inside the VCL file, but in this case credentials are stored in a [dictionary](https://docs.fastly.com/en/guides/working-with-dictionaries-using-the-web-interface#working-with-dictionaries-using-vcl-snippets).
+Usernames and passwords can be stored inside the VCL file, but in this case credentials are stored in a [dictionary](https://docs.fastly.com/en/guides/working-with-dictionaries#working-with-dictionaries-using-vcl-snippets).
 
 !!! note
     To make this example work, you must run [[= product_name =]] in version 3.3.16 or later, or 4.5.
@@ -484,5 +484,3 @@ fastly vcl snippet create --name="BasicAuth recv" --version=active --autoclone -
 fastly vcl snippet create --name="BasicAuth error" --version=latest --priority 100 --type error --content=snippet_basic_auth_error.vcl
 fastly service-version activate --version=latest
 ```
-
- 

docs/guide/cache/http_cache.md

@@ -9,8 +9,8 @@ to make Varnish and Fastly act as the view cache for the system.
 This and other features allow [[= product_name =]] to be scaled up to serve high traffic websites and applications.
 
 HTTP cache is handled by the [ezplatform-http-cache](https://github.com/ezsystems/ezplatform-http-cache) bundle,
-which extends [friendsofsymfony/http-cache-bundle](https://foshttpcachebundle.readthedocs.io/en/2.8.0/),
-a Symfony community bundle that in turn extends [Symfony HTTP cache](http://symfony.com/doc/5.1/http_cache.html).
+which extends [friendsofsymfony/http-cache-bundle](https://foshttpcachebundle.readthedocs.io/en/stable/),
+a Symfony community bundle that in turn extends [Symfony HTTP cache](https://symfony.com/doc/5.x/http_cache.html).
 
 For content view responses coming from [[= product_name =]] itself, this means that:
 

docs/guide/cache/http_cache_config.md

@@ -29,7 +29,7 @@ As the system takes care of purges, the cache should not become stale with the e
 A few redirect and error pages are served through the content view system. If you set a high `default_ttl`, they can also be served from cache.
 
 To avoid this, the installation ships with configuration to match these specific situations and set a much lower TTL.
-[FOSHttpCacheBundle matching rules](http://foshttpcachebundle.readthedocs.io/en/2.8.0/reference/configuration/headers.html) enables you to specify a different TTL:
+[FOSHttpCacheBundle matching rules](https://foshttpcachebundle.readthedocs.io/en/stable/reference/configuration/headers.html) enables you to specify a different TTL:
 
 ``` yaml
 fos_http_cache:

docs/guide/cache/symfony_reverse_proxy.md

@@ -61,8 +61,8 @@ For more information on how to configure Fastly with [[= product_name =]], see [
 
     Support for Fastly Shielding was added in [[= product_name =]] v3.3.24 and v4.1.6.
 
-    When you extend [FOSHttpCacheBundle](https://foshttpcachebundle.readthedocs.io/en/2.9.1/),
-    you can also adapt your VCL further with [FOSHttpCache documentation](http://foshttpcache.readthedocs.org/en/latest/varnish-configuration.html)
+    When you extend [FOSHttpCacheBundle](https://foshttpcachebundle.readthedocs.io/en/stable/),
+    you can also adapt your VCL further with [FOSHttpCache documentation](https://foshttpcache.readthedocs.io/en/stable/varnish-configuration.html)
     to use additional features.
 
 ## Configure Varnish and Fastly
@@ -77,7 +77,7 @@ Failing to configure reverse proxies correctly may introduce several problems, i
 
 ### Configure Symfony front controller
 
-You need to consider your `TrustedProxy` configuration when you use Symfony [behind a load balancer or a reverse proxy.](https://symfony.com/doc/5.1/deployment/proxies.html)
+You need to consider your `TrustedProxy` configuration when you use Symfony [behind a load balancer or a reverse proxy.](https://symfony.com/doc/5.x/deployment/proxies.html)
 
 Set the following environment variable:
 - `TRUSTED_PROXIES`: String with trusted IP, multiple proxies can be configured with a comma, for example, `TRUSTED_PROXIES="192.0.0.1,10.0.0.0/8"`
@@ -91,7 +91,7 @@ framework:
 
 !!! caution "Careful when trusting dynamic IP using `REMOTE_ADDR` value or similar"
 
-    On Platform.sh, Varnish does not have a static IP, like with [AWS LB](https://symfony.com/doc/5.1/deployment/proxies.html#but-what-if-the-ip-of-my-reverse-proxy-changes-constantly).
+    On Platform.sh, Varnish does not have a static IP, like with [AWS LB](https://symfony.com/doc/5.x/deployment/proxies.html#but-what-if-the-ip-of-my-reverse-proxy-changes-constantly).
     For this reason, the `TRUSTED_PROXIES` env variable supports being set to value `REMOTE_ADDR`, which is equal to:
 
     ```php
@@ -104,7 +104,7 @@ framework:
     Make sure that **all** traffic always comes from the trusted proxy/load balancer,
     and that there is no other way to configure it.
 
-When using Fastly, you need to set `trusted_proxies` according to the [IP ranges used by Fastly](https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges).
+When using Fastly, you need to set `trusted_proxies` according to the [IP ranges used by Fastly](https://www.fastly.com/documentation/reference/api/utils/public-ip-list/).
 
 !!! tip
 
@@ -194,7 +194,7 @@ For more information about configuring Captcha fields, see [Captcha field](../..
 ### Use Fastly as HttpCache proxy
 
 [Fastly](https://www.fastly.com/) delivers Varnish as a CDN service and is supported with [[= product_name =]].
-To learn how it works, see [Fastly documentation](https://docs.fastly.com/guides/basic-concepts/how-fastlys-cdn-service-works).
+To learn how it works, see [Fastly documentation](https://docs.fastly.com/en/guides/using-fastlys-global-pop-network).
 
 #### Configure Fastly in YML
 
@@ -230,16 +230,16 @@ FASTLY_KEY="token"
 
 #### Configure Fastly on Platform.sh
 
-If you use Platform.sh, it is recommended to configure all environment variables through [Platform.sh variables](https://docs.platform.sh/frameworks/ibexa/fastly.html).
+If you use Platform.sh, it is recommended to configure all environment variables through [Platform.sh variables](https://docs.platform.sh/guides/ibexa/fastly.html).
 In [[= product_name =]], Varnish is enabled by default. To use Fastly, first you must 
-[disable Varnish](https://docs.platform.sh/frameworks/ibexa/fastly.html#remove-varnish-configuration) 
+[disable Varnish](https://docs.platform.sh/guides/ibexa/fastly.html#remove-varnish-configuration) 
 
 #### Get Fastly service ID and API token
 
-To get the service ID, log in to http://fastly.com. In the upper menu, click the **CONFIGURE** tab.
+To get the service ID, log in to https://www.fastly.com/. In the upper menu, click the **CONFIGURE** tab.
 The service ID is displayed next to the name of your service on any page.
 
-For instructions on how to generate a Fastly API token, see [the Fastly guide](https://docs.fastly.com/guides/account-management-and-security/using-api-tokens).
+For instructions on how to generate a Fastly API token, see [the Fastly guide](https://docs.fastly.com/en/guides/using-api-tokens).
 The API token needs the `purge_all` an `purge_select` scopes.
 
 ### Configuration examples
@@ -272,7 +272,7 @@ fastcgi_param HTTPCACHE_PURGE_SERVER "http://varnish:80";
 
 Example for Platform.sh:
 
-You can configure environment variables through [Platform.sh variables](https://docs.platform.sh/frameworks/ibexa/fastly.html).
+You can configure environment variables through [Platform.sh variables](https://docs.platform.sh/guides/ibexa/fastly.html).
 
 !!! tip