Slow read attack in HTTP/2
jsharan15 at gmail.com
Fri Aug 19 12:37:46 UTC 2016
Thanks for the response.
Would like to know what happens in the following scenario,
Client sets its initial congestion window size to be very small and
requests for a large data. It updates the window size everytime when it
gets exhausted with a small increment (so send_timeout wont happen as
writes happens always but in a very small amount). In this case won't the
connection remain until the server flushes all the data to the client which
has very less window size?
If the client opens many such connections with many streams, each
requesting for a very large data, then won't it cause DOS?
On Fri, Aug 19, 2016 at 5:28 PM, Valentin V. Bartenev <vbart at nginx.com>
> On Friday 19 August 2016 17:06:41 Sharan J wrote:
> > Hi,
> > Would like to know what timeouts should be configured to mitigate slow
> > attack in HTTP/2.
> A quote from the commit:
> | Now almost all the request timeouts work like in HTTP/1.x connections,
> | the "client_header_timeout", "client_body_timeout", and "send_timeout"
> | respected. These timeouts close the request.
> and the documentation links:
> > Referred ->
> > https://trac.nginx.org/nginx/changeset/4ba91a4c66a3010e50b84fc73f05e8
> > Could not understand what you have done when all streams are stuck on
> > exhausted connection or stream windows. Please can you explain me the
> Each stream has its own timeout configured by the directives mentioned
> If there's no progress on a stream during one of these timeouts then the
> is closed.
> wbr, Valentin V. Bartenev
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx