Skip to content

Commit 5728609

Browse files
committed
general cleanup of the entire web path cache resolver RST documentation opening paragraphs
1 parent fc6b3e0 commit 5728609

File tree

1 file changed

+17
-13
lines changed

1 file changed

+17
-13
lines changed

Resources/doc/cache-resolver/web_path.rst

+17-13
Original file line numberDiff line numberDiff line change
@@ -4,22 +4,26 @@
44
Web Path Resolver
55
=================
66

7-
The ``WebPathResolver`` resolver enabled cache resolution using the
8-
web path of your application. The resulting web path is computed by
9-
taking a number of factors into account, including the `request context`_
10-
as provided by the Symfony HTTP kernel.
7+
This cache resolver (``WebPathResolver``) enables cache resolution for
8+
local, web-path-based setups. This means images will be cached on your
9+
local filesystem, within the web path of your Symfony application.
10+
11+
The resulting web path is computed by taking a number of factors into
12+
account, including the `request context`_, as provided by the Symfony
13+
HTTP kernel.
1114

1215
.. tip::
1316

14-
The request context is most notably used to determine the HTTP scheme
15-
prepended to the final URL. If you use a proxy to offload TLS traffic
16-
decryption and need the resolver to generate HTTPS URLS, you will need
17-
to configure Symfony's `trusted proxies`_ appropriately. If you
18-
`embed controllers`_ in your templates, ``localhost`` must be added to
19-
your trusted proxy configuration.
17+
The `request context`_ is most notably used to determine the HTTP
18+
scheme used for the final URL. If you use a proxy to offload TLS
19+
traffic decryption and need the resolver to generate secure URLs,
20+
you will need to appropriately configure Symfony's `trusted proxies`_.
21+
If you utilize `embedded controllers`_ in your templates, you must
22+
add ``localhost`` to your trusted proxy configuration.
2023

21-
The request context is also used to determine the port to specify,
22-
should it differ from the standard HTTP/HTTPS (80/443) ports.
24+
Also, the `request context`_ is used to determine the port of the
25+
resulting URL, should it differ from the standard HTTP/HTTPS (80/443)
26+
ports.
2327

2428

2529
Configuration
@@ -82,4 +86,4 @@ filter set using the following configuration.
8286
8387
.. _`request context`: http://symfony.com/doc/current/components/http_foundation.html#request
8488
.. _`trusted proxies`: https://symfony.com/doc/current/request/load_balancer_reverse_proxy.html#solution-trusted-proxies
85-
.. _`embed controllers`: https://symfony.com/doc/current/templating/embedding_controllers.html
89+
.. _`embedded controllers`: https://symfony.com/doc/current/templating/embedding_controllers.html

0 commit comments

Comments
 (0)