Julien Viet

I think in 4.1 we should add a connection acquisition timeout and have the global timeout only for the HTTP request operation, now this is possible with the new pool...

this might be lot of overhead because a context is created each time an HttpServerRequest is handled.

what do you mean by "feature" ?

it is not clear why this is needed, can you elaborate ?

can you upgrade to 3.9 ? that's the only version of Vert.x 3 we are currently supporting

I'll have a look at the reproducer, thanks

can you provide a recap with all the precise intructions to reproduce it @agapic ?

thank you On Fri, Mar 11, 2022 at 7:05 AM Andrew Gapic ***@***.***> wrote: > Yeah I will put together a new repo with complete code that includes NGINX >...

"Now when client 2 connects to the service, the request handler appears to be re-using the request headers from client 1. " : can you elaborate why nginx will resend...

when I try the reproducer I get: ``` julien@Juliens-MacBook-Pro vertx-nginx-websocket-repro % ./force-response.sh 200 ws://localhost:9090/ws A848EC3A-9EF1-4A2A-8052-5EA8CEA9E386 looping 200 once-per-second Connected (press CTRL+C to quit) ``` is that what is supposed to...