raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

Actually implement proper cascading

Browse source
This commit is contained in:
Konrad Malawski 2015-09-25 15:50:11 +02:00
parent b1f9f77a17
commit cad852025d
12 changed files with 260 additions and 267 deletions
Download patch file Download diff file Expand all files Collapse all files

17
akka-docs-dev/rst/scala/http/common/http-model.rst
View file

@ -253,11 +253,14 @@ provided to parse (or render to) Strings or byte arrays.
.. note::
Various parsing and rendering settings are available to tweak in the configuration under ``akka.http.client[.parsing]``,
``akka.http.server[.parsing]`` and ``akka.http.host-connection-pool[.client.parsing]``. Please note that while each of
these sections expose the same parsing options, they will only be used for their respective APIs. For example, changing
a setting inside ``akka.http.client.parsing`` **does not** change the same value in ``akka.http.host-connection-pool.client.parsing``,
as they are different APIs.
``akka.http.server[.parsing]`` and ``akka.http.host-connection-pool[.client.parsing]``, with defaults for all of these
being defined in the ``akka.http.parsing`` configuration section.
You can check which settings to tweak for which method exposed on the Http object by inspecting their ScalaDoc.
In general though it's as simple as "pool" backed services use the ``host-connection-pool`` section, other clients
which expose ``Flow`` use the ``client`` section, and the server side uses the ``server`` configuration section.
For example, if you want to change a parsing setting for all components, you can set the ``akka.http.parsing.illegal-header-warnings = off``
value. However this setting can be stil overriden by the more specific sections, like for example ``akka.http.server.parsing.illegal-header-warnings = on``.
In this case both ``client`` and ``host-connection-pool`` APIs will see the setting ``off``, however the server will see ``on``.
In the case of ``akka.http.host-connection-pool.client`` settings, they default to settings set in ``akka.http.client``,
and can override them if needed. This is useful, since both ``client`` and ``host-connection-pool`` APIs,
such as the Client API ``Http().outgoingConnection`` or the Host Connection Pool APIs ``Http().singleRequest`` or ``Http().superPool``,
usually need the same settings, however the ``server`` most likely has a very different set of settings.