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

!htp #19528 HttpServerBluePrint: close connection on request entity cancellation

Browse source
This commit is contained in:
Anton Karamanov 2016-02-05 11:23:57 +03:00 • committed by Anton Karamanov
parent 6ef9ab3276
commit af3fc0c9a6
10 changed files with 185 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
akka-docs/rst/java/http/client-side/connection-level.rst
View file

@ -53,6 +53,10 @@ The connection can also be closed by the server.
An application can actively trigger the closing of the connection by completing the request stream. In this case the
underlying TCP connection will be closed when the last pending response has been received.
The connection will also be closed if the response entity is cancelled (e.g. by attaching it to ``Sink.cancelled()``)
or consumed only partially (e.g. by using ``take`` combinator). In order to prevent this behaviour the entity should be
explicitly drained by attaching it to ``Sink.ignore()``.
Timeouts
--------

4
akka-docs/rst/java/http/server-side/low-level-server-side-api.rst
View file

@ -130,6 +130,10 @@ connection. An often times more convenient alternative is to explicitly add a ``
``HttpResponse``. This response will then be the last one on the connection and the server will actively close the
connection when it has been sent out.
Connection will also be closed if request entity has been cancelled (e.g. by attaching it to ``Sink.cancelled()``)
or consumed only partially (e.g. by using ``take`` combinator). In order to prevent this behaviour entity should be
explicitly drained by attaching it to ``Sink.ignore()``.
.. _serverSideHTTPS-java: