Hello,
On Mon, 24 Sep 2018 at 14:42, Maciej Małeta <[email protected]> wrote: > > Hi, > > i have problem with my haproxy 1.8.14 > when i want start it, i get error: tune.ssl.force-private-cache' cannot > handle unexpected argument 'false' > in version 1.5 it's work fine > what is wrong in 'false' option? > I would be very grateful for your help. tune.ssl.force-private-cache is an option that does not accept any arguments, including true or false. Unfortunately, unknown additional arguments are silently ignored in haproxy <= 1.5. This was fixed in haproxy 1.6; which correctly rejects this invalid configuration. What that means is that by configuring: tune.ssl.force-private-cache false You actually enabled private cache in haproxy 1.5, causing SSL cache not to be shared between processes. However, this obviously only affects you when you are using nbproc > 1. I can see why the documentation about tune.ssl.force-private-cache would be confusing, as it talks about being a boolean (which is correct, internally, but doesn't belong in the documentation and only makes users think they need to provide a boolean). I will send a patch to replace "boolean" with "option" in the documentation, that should clear up this misunderstanding. Regards, Lukas
