> >> Yes sure :-) Feel free to send a patch regarding this otherwise I may
> >> forget
> >> just like I forgot to remove "1.5" from the stats page before releasing
> >> 1.7.1.
>
> Attached.
>
> Marcin
> --- doc/configuration.txt.old 2016-12-12 22:57:04.0 +0100
> +++
On 12/13/2016 11:25 AM, Willy Tarreau wrote:
>> I think we'll definitely need to have some string-oriented operators. We
>> could implement them using converters (eg: append and compare mostly), but
>> we also thought that we could replace every sample fetch with a converter
>> and allow all
Hi Marcin,
On Tue, Dec 13, 2016 at 10:53:05AM +0100, Marcin Deranek wrote:
> On 12/12/2016 03:14 PM, Willy Tarreau wrote:
> > Just merged now, thanks. A few weeks ago someone needed it, I guess it
> > was for logging, and I thought we had it though it was not the case, so
> > I realized we were
On 12/12/2016 03:14 PM, Willy Tarreau wrote:
> Just merged now, thanks. A few weeks ago someone needed it, I guess it
> was for logging, and I thought we had it though it was not the case, so
> I realized we were missing it. In fact we still have quite a number of
> fields available as log tags
Hi Marcin,
On Mon, Dec 12, 2016 at 02:08:05PM +0100, Marcin Deranek wrote:
> Hi,
> These 2 patches add ability to fetch frontend/backend name in your
> logic, so they can be used later to make routing decisions (fe_name) or
> taking some actions based on backend which responded to request
Hi,
These 2 patches add ability to fetch frontend/backend name in your
logic, so they can be used later to make routing decisions (fe_name) or
taking some actions based on backend which responded to request (be_name).
In our case we needed a fetcher to be able to extract information we
needed from
6 matches
Mail list logo
