OK so I'm going to merge this now, it looks quite good and proves much
more useful even in testing than what we've been dealing with over the
last few years. If anybody wants to suggest a change, don't worry, we're
still in development, we can change it later.
Thanks for your comments!
Willy
---
Hi guys,
First, thanks a lot, that's *exactly* the type of feedback I was waiting
for.
On Tue, Aug 23, 2016 at 12:40:58PM +0200, Olivier Doucet wrote:
> 2016-08-23 12:22 GMT+02:00 Conrad Hoffmann :
(...)
> > So with that reasoning, I guess I would love to see:
> > - all new variables created tha
Hi all,
2016-08-23 12:22 GMT+02:00 Conrad Hoffmann :
> Hi,
>
> first of all, it's great that this is being tackled. Thanks a lot!
>
> I don't have a very strong opinion on most of the details, but my thoughts
> are somewhere along these lines:
>
> - If possible, the most detailed information s
Hi,
first of all, it's great that this is being tackled. Thanks a lot!
I don't have a very strong opinion on most of the details, but my thoughts
are somewhere along these lines:
- If possible, the most detailed information should be made available,
not neccessarily by default, but at least
On Tue, Aug 23, 2016 at 11:34:39AM +0200, Willy Tarreau wrote:
> Maybe something between all of this could consist in this :
>
> - we create a new date field (eg: %tr) to note the date the request
> starts to arrive (end of the idle period)
> - we use a new field for the request-only time
Hi all,
For quite some time now I've been annoyed by the browsers' preconnect
feature causing unexploitable %Tq in the logs. But to defend the browsers,
we're having the same issue with the keep-alive feature as well.
So I planned to change %Tq to %Ti+%Tq where Ti would be the idle time
before th
6 matches
Mail list logo