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

=htc,doc more docs on EntityStreamSizeException

Browse source
This commit is contained in:
Konrad Malawski 2015-12-13 16:17:20 +00:00
parent b16b1692e3
commit 9d5fcabbd6
2 changed files with 14 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -166,6 +166,7 @@ them. This check makes sure that the total entity size is less than or equal to
However, a single global limit for all requests (or responses) is often too inflexible for applications that need to
allow large limits for *some* requests (or responses) but want to clamp down on all messages not belonging into that
group.
In order to give you maximum flexibility in defining entity size limits according to your needs the ``HttpEntity``
features a ``withSizeLimit`` method, which lets you adjust the globally configured maximum size for this particular
entity, be it to increase or decrease any previously set value.
@ -173,7 +174,7 @@ This means that your application will receive all requests (or responses) from t
``Content-Length`` exceeds the configured limit (because you might want to increase the limit yourself).
Only when the actual data stream ``Source`` contained in the entity is materialized will the boundary checks be
actually applied. In case the length verification fails the respective stream will be terminated with an
``EntityStreamException`` either directly at materialization time (if the ``Content-Length`` is known) or whenever more
:class:`EntityStreamSizeException` either directly at materialization time (if the ``Content-Length`` is known) or whenever more
data bytes than allowed have been read.
When called on ``Strict`` entities the ``withSizeLimit`` method will return the entity itself if the length is within