❦ 27 janvier 2017 20:54 -0600, David Morton :
> I have a pretty default Ubuntu 16.04 image on AWS set up with the
> haproxy 1.7 ppa package. I'm not seeing a /var/log/haproxy log file.
>
>
> haproxy config is:
>
> log /dev/loglocal0
> log /dev/loglocal1
Hi,
thanks for the bug repport. I already encoutered with another function
than redirect. Can you try the join patch ?
Thierry
On Fri, 27 Jan 2017 22:50:00 +
Jesse Schulman wrote:
> I've found what seems to be a bug when I log from within a Lua sample fetch
> that I
I have a pretty default Ubuntu 16.04 image on AWS set up with the
haproxy 1.7 ppa package. I'm not seeing a /var/log/haproxy log file.
haproxy config is:
log /dev/log local0
log /dev/log local1 notice
chroot /var/lib/haproxy
and rsyslog is:
# Create an additional socket in
I've found what seems to be a bug when I log from within a Lua sample fetch
that I am using to determine a redirect URL. It seems that whatever is
logged from the lua script is written to the log file as expected, but it
also is replacing the response, making the response invalid and breaking
the
On 2017/1/27 15:31, Ciprian Dorin Craciun wrote:
> On Fri, Jan 27, 2017 at 10:24 PM, Patrick Hemmer
> wrote:
>> Something that might satisfy both requests, why not just append to the
>> existing request-id?
>>
>> unique-id-format %[req.hdr(X-Request-ID)],%{+X}o\
>>
On Fri, Jan 27, 2017 at 10:24 PM, Patrick Hemmer
wrote:
> Something that might satisfy both requests, why not just append to the
> existing request-id?
>
> unique-id-format %[req.hdr(X-Request-ID)],%{+X}o\
> %ci:%cp_%fi:%fp_%Ts_%rt:%pid
>
> This does result in a
On 2017/1/27 14:38, Cyril Bonté wrote:
> Le 27/01/2017 à 20:11, Ciprian Dorin Craciun a écrit :
>> On Fri, Jan 27, 2017 at 9:01 PM, Cyril Bonté
>> wrote:
>>> Instead of using "unique-id-header" and temporary headers, you can
>>> use the
>>> "unique-id" fetch sample [1] :
Le 27/01/2017 à 20:11, Ciprian Dorin Craciun a écrit :
On Fri, Jan 27, 2017 at 9:01 PM, Cyril Bonté wrote:
Instead of using "unique-id-header" and temporary headers, you can use the
"unique-id" fetch sample [1] :
frontend public
bind *:80
unique-id-format %{+X}o\
On Fri, Jan 27, 2017 at 9:01 PM, Cyril Bonté wrote:
> Instead of using "unique-id-header" and temporary headers, you can use the
> "unique-id" fetch sample [1] :
>
> frontend public
> bind *:80
> unique-id-format %{+X}o\ %ci:%cp_%fi:%fp_%Ts_%rt:%pid
>
Hi,
Le 26/01/2017 à 23:10, sendmaildevnull a écrit :
I'm trying generate a unique-id-header only if one is not already
provided in the request. If I provide the header in my request to
haproxy I end up with duplicate headers, one with auto generated header
and another with the user provided
On Wed, Jan 11, 2017 at 8:59 PM, Willy Tarreau wrote:
>> [I can't speak with much confidence as this is the first time I see
>> the HAProxy code, but...]
>>
>>
>> >From what I see the main culprit for the connection close is the code:
>>
>> [starting with line 4225 in
On Fri, Jan 27, 2017 at 12:10 AM, sendmaildevnull
wrote:
> I'm trying generate a unique-id-header only if one is not already provided
> in the request. If I provide the header in my request to haproxy I end up
> with duplicate headers, one with auto generated header and
Hello,
So here's patch, which includes all functionalities I think about.
It propagates the response for every tracking server without changing it
and without intercepting it. In my opinion we should propagate relative
and absolute weights, because if you use weight=0 server's to offload
checks
Hi All,
Sorry I missed it
I'll see what I can do to fix it asap.
Thanks for reporting.
Baptiste
On Thu, Jan 26, 2017 at 6:40 PM, Lukas Tribus wrote:
> Hello,
>
>
>
> Am 29.11.2016 um 09:53 schrieb Willy Tarreau:
>
>> Hi Joshua,
>>
>> [ccing Baptiste]
>>
>> On Tue, Nov
14 matches
Mail list logo