tree ac21324937c5368de840ccecd139f35c9913cb08
parent 59070784fcac855b1a7e6da7c239800aeed622bb
author Willy Tarreau <w@1wt.eu> 1507125532 +0200
committer Willy Tarreau <w@1wt.eu> 1507126437 +0200
encoding latin1

BUG/MINOR: tcp-check: don't initialize then break a connection starting with a comment

The following config :

    backend tcp9000
        option tcp-check
        tcp-check comment "this is a comment"
        tcp-check connect port 10000
        server srv 127.0.0.1:9000 check inter 1s

will result in a connection being first made to port 9000 then immediately
destroyed and re-created on port 10000, because the first rule is a comment
and doesn't match the test for the first rule being a connect(). It's
mostly harmless (unless the server really must not receive empty
connections) and the workaround simply consists in removing the comment.

Let's proceed like in other places where we simply skip leading comments.
A new function was made to make this lookup les boring. The fix should be
backported to 1.7 and 1.6.