Hi Lukas, On Mon, Jul 27, 2020 at 12:58:29PM +0200, Lukas Tribus wrote: > Hello, > > > On Thu, 23 Jul 2020 at 14:34, Willy Tarreau <w...@1wt.eu> wrote: > > > defaults > > > http-reuse always > > > > > > backend abuse > > > timeout server 60s > > > balance roundrobin > > > hash-balance-factor 0 > > > server s_abuse u...@abuse.sock send-proxy-v2 maxconn 4 > > > > > > listen l_abuse > > > bind u...@abuse.sock accept-proxy > > > http-request set-var(req.delay) int(500) > > > http-request lua.add_delay > > > server xxxx 192.168.000.aaa:80 maxconn 1 > > > server yyyy 192.168.000.bbb:80 maxconn 1 > > > server zzzzz 192.168.000.ccc:80 maxconn 1 > > > > > > Is it OK ? Because i have no warning when verifying the configuration, or > > > should i add a "http-reuse never" in "backend abuse" ? > > > > It is now properly dealt with, by marking the connection private, which > > means it will not be shared at all. So what you'll see simply is that > > there is no reuse for connections employing send-proxy. So your config > > is safe, but you will just not benefit from the reuse. > > > > Anyway it's generally not a good idea to use proxy protocol over HTTP > > from an HTTP-aware agent. Better use Forward/X-Forwarded-for that passes > > the info per request and that nowadays everyone can consume. > > However on a unix domain socket like this we never had this issue in > the first place, as connection-reuse cannot be used on it by > definition, correct?
No, it doesn't change anything. We consider the connection, the protocol family it uses is irrelevant. Regards, Willy
