Hi, is there a way to configure timeouts for requests?

# http4k

[Cosmin Victor Celea]

Hi, is there a way to configure timeouts for requests?

[dave]

for outgoing you can just configure the client. for incoming it's something I've actually never seen done before TBH..

[Cosmin Victor Celea]

For incoming, we wrote our own throttling logic, and we had a pentester testing the app, and we discovered the throttling breaks because of hanging requests.

[dave]

can you reuse something from resilience4k maybe?

[Cosmin Victor Celea]

will check

[James Richardson]

You might consider a proxy in front of the jvm to deal with stuff like that. Varnish and others can help mitigate slow loris type attacks.

[Fantayeneh]

I think for undertow the idle timeout is already exposed. <http://UndertowOptions.NO|UndertowOptions.NO>_REQUEST_TIMEOUT
It can also be don for netty server if we add the ReadTimeoutHandler in the server pipeline

[Cosmin Victor Celea]

does not seem to work for undertow

[Cosmin Victor Celea]

the request still stays open

[Cosmin Victor Celea]

even after the configured time has passed

[Cosmin Victor Celea]

I actually found a solution using withTimeoutOrNull inside a filter that wraps the request. Bad idea @dave ?