@@ -45,7 +45,7 @@ clients.
4545 );
4646 }
4747
48- You will find all available configuration at the
48+ You can find all available configuration at the
4949:doc: `full configuration </integrations/symfony-full-configuration >` page.
5050
5151Usage
@@ -234,7 +234,7 @@ Additionally you can configure any of the ``php-http/plugins`` specifically on
234234a client. For some plugins this is the only place where they can be configured.
235235The order in which you specify the plugins **does ** matter.
236236
237- Configure plugins directly on the client:
237+ You can configure many of the plugins directly on the client:
238238
239239.. code-block :: yaml
240240
@@ -256,7 +256,12 @@ Configure plugins directly on the client:
256256 password : ' p4ssw0rd'
257257
258258
259- Configure the cache plugin globally and use it in the ``acme `` client:
259+ See :doc: `full configuration </integrations/symfony-full-configuration >` for
260+ the full list of plugins you can configure.
261+
262+ Alternatively, the same configuration also works on a global level. With this,
263+ you can configure plugins once and then use them in several clients. The plugin
264+ service names follow the pattern ``httplug.plugin.<name> ``:
260265
261266.. code-block :: yaml
262267
@@ -270,8 +275,14 @@ Configure the cache plugin globally and use it in the ``acme`` client:
270275 factory : ' httplug.factory.guzzle6'
271276 plugins :
272277 - ' httplug.plugin.cache'
278+ app :
279+ plugins :
280+ - ' httplug.plugin.cache'
273281
274- Configure a service for your custom plugin and use it in the client:
282+ To use a custom plugin or when you need specific configuration that is not
283+ covered by the bundle configuration, you can configure the plugin as a normal
284+ symfony service and then reference that service name in the plugin list of your
285+ client:
275286
276287.. code-block :: yaml
277288
0 commit comments