On Thu, Apr 15, 2010 at 01:02:27PM +0200, Cyril Bouthors wrote: > On 15 Apr 2010, [email protected] wrote: > > > It's not that easy. We only know about an option setting once the > > whole section is parsed, and we don't know if it was explicitly set or > > inherited from the defaults section. Also, I generally prefer to warn > > users about dangerous option combinations than let them believe their > > option has any effect. > > OK, then instead of having "option forceclose" in the "defaults" > sections and "no option forceclose" in each "mode tcp" section, I'll do > the opposite: nothing as default and forceclose only in HTTP mode.
that's one possibility. Many people use another method : they have one "defaults" section for all HTTP settings, then they declare all their HTTP sections, then a new "defaults" section for all TCP settings and they declare their TCP sections. Since one defaults section completely replaces the previous one for the following sections, you can easily proceed that way. Willy
