I’m not experiencing any issue at the moment. i’m actually doing prevention from security perspective.
I’m hardenning the security configuration for caddy in my application stack. By looking at the TLS configuration, the logging and now i’m working on the network aspect (on HTTP).
I did some research and it seems that the philosophy of caddy is to be secured by default 
I also dig a bit futher about the pooling, this post : Proxy - pre-warmed connections - understanding keepalive. I didn’t find documentation about connection pooling in caddy. is it handled “natively” by Go ?
So the risk is not revelant since if we have the same connection it will reuse an open one ? is there a value to close idle connection from the pool ?
I’m also looking for a way to sets a timeout when caddy transmit a response to the client between two successive write operations. Do you know which directives can help me ?