Hi Shawn,
Le 16/05/2015 00:10, Shawn Heisey a écrit :
I found what I think is a couple of bugs. I'm running 1.5.12.
If "mode http" or "option forwardfor" are in the defaults section, I
cannot get a frontend configured with "mode tcp" to work.
The "mode tcp" config is not overriding the default choice, it operates
in the http mode specified in defaults.
It should not, are you sure this is not because you're using a backend
with "mode http" enabled ? both have to be in tcp mode to disable the
defaults, as it is valid to have a frontend in tcp mode with a backend
in http mode.
If option forwardfor is in defaults, config validation fails when the
frontend specifies tcp mode. I could not find a way to turn off
forwardfor in the frontend when it's enabled in defaults ... but I think
when the frontend mode is tcp, that inherited option should probably be
ignored. I can understand a config error if forwardfor is explicitly
configured in the frontend.
I guess you are seeing a warning, not en error, and then the validation
shouldn't fail.
Sometimes, you can use an interesting trick : do you know you can
declare several "defaults" sections ? It allows to declare a "defaults"
one for you "http" frontends/backends, and another one for the tcp ones.
--
Cyril Bonté
