Le lundi 20 juin 2011 23:52:42, Willy Tarreau a écrit :
> In my opinion these warnings do not help much here because there is already
> a valid http-keep-alive timeout in the frontends (inherited from defaults)
> so at most the backend's is ignored but the frontend's applies. Well, at
> least it catches the incoherent cases where one believes the backend's
> would apply. I'm dubious about the risk of false positive, while what we're
> looking for is mainly the situation where the frontend's is not set while
> the backend's is set.

Indeed, I tried to produce the worst test case to see how verbose it was.
I also worked on another version which is much less verbose (only notify that 
a HTTP frontend with no timeout won't use the backends ones, when they have).

> For instance, if both an HTTP and a TCP frontend make use of the same
> backend, I think it can be hard to write a config without any warning.
> Maybe we should instead try to think about a way to apply more adequate
> semantics on such timeouts so that they do what people would think first.
> For instance, maybe if we consider that the backend's timeout overrides
> the frontend's even in such situations, it makes sense (we should be even
> more careful than for the warnings).

That was my first goal before trying to add warnings.
It was nearly OK for http-keep-alive timeout (I only have to fix a side effect 
when the frontend is in tcp). But for http-request timeout, I can't see how 
that would work. The only workaround I saw was to provide a warning.

But well, it doesn't prevent 1.4.16 to be released, as you said it "works as 
designed" and it can be fixed quite easily in the configuration ;-)

-- 
Cyril Bonté

Reply via email to