Ravi,

I accept, but we are using 1.3.x version almost from 1.5 years and the configuration was really worked amazing, steel won't change through config,

I'm afraid I don't quite follow this statement. You're unable or unwilling to change the config? Is steel a person/client, or do you mean you still won't change the config? Regardless...

so can we disable these alerts from haproxy bin through compiling any options need to set while compile it, need your help to fix it.

I'm not aware of a way you can disable these warnings through compile time options, but I'm hardly an expert. They are just warnings though, your configuration should still work so you can safely ignore them. If haproxy isn't working you should probably look and see if you have any [ERROR] statements in with the warnings.

Another option would be to move mode http out of the defaults section, and into each :80 listen statement. Then you will have mode http on your http listeners and mode tcp on your https/443 listeners and you shouldn't generate any more warnings. I see that you already have the statement in your :80 block, so you would just need to remove it from the defaults section.

-JohnF

Reply via email to