@@ -45,7 +45,7 @@ clients.
45
45
);
46
46
}
47
47
48
- You will find all available configuration at the
48
+ You can find all available configuration at the
49
49
:doc: `full configuration </integrations/symfony-full-configuration >` page.
50
50
51
51
Usage
@@ -234,7 +234,7 @@ Additionally you can configure any of the ``php-http/plugins`` specifically on
234
234
a client. For some plugins this is the only place where they can be configured.
235
235
The order in which you specify the plugins **does ** matter.
236
236
237
- Configure plugins directly on the client:
237
+ You can configure many of the plugins directly on the client:
238
238
239
239
.. code-block :: yaml
240
240
@@ -256,7 +256,12 @@ Configure plugins directly on the client:
256
256
password : ' p4ssw0rd'
257
257
258
258
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> ``:
260
265
261
266
.. code-block :: yaml
262
267
@@ -270,8 +275,14 @@ Configure the cache plugin globally and use it in the ``acme`` client:
270
275
factory : ' httplug.factory.guzzle6'
271
276
plugins :
272
277
- ' httplug.plugin.cache'
278
+ app :
279
+ plugins :
280
+ - ' httplug.plugin.cache'
273
281
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:
275
286
276
287
.. code-block :: yaml
277
288
0 commit comments