Re: "timeout client" weird behaviour in 1.3.22

From: Cyril Bouthors <cyril#bouthors.org>
Date: Thu, 15 Apr 2010 13:02:27 +0200

On 15 Apr 2010, w#1wt.eu 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.

Thanks.

-- 
Cyril Bouthors

Received on 2010/04/15 13:02