Awesome, thanks for the fast turnaround.
B.
> On 29 Nov 2019, at 11:04, Christopher Faulet wrote:
>
> Le 29/11/2019 à 10:46, Robert Samuel Newson a écrit :
>> Hi,
>> I've discovered it is possible to make haproxy (2.0.9 and 2.0.10, at least)
>> produce duplicate h
Hi,
I've discovered it is possible to make haproxy (2.0.9 and 2.0.10, at least)
produce duplicate headers using the set-header directive (which is defined as
"This does the same as "http-request add-header" except that the header name
is first removed if it existed.").
This only happens when
We've found that just switching back to 1.7.9 makes this issue disappear. It's
a really hard one to pin down though. It's quite rare and we've had no luck
building a reliable reproducing script.
Is there anything more we can provide to give insight into why haproxy might
sometimes hang during
.
> On 1 Mar 2018, at 11:06, Willy Tarreau <w...@1wt.eu> wrote:
>
> On Thu, Mar 01, 2018 at 09:38:10AM +, Robert Samuel Newson wrote:
>> Yup, agreed, the frame-only transfers are only really implied in the spec
>> (8.1.2.6's, "A request or response that inclu
unds right to me,
and I'll keep an eye out for commits, I'm happy to test it out.
Thanks!
B.
> On 1 Mar 2018, at 06:16, Willy Tarreau <w...@1wt.eu> wrote:
>
> Hi Robert,
>
> On Tue, Feb 27, 2018 at 08:26:01PM +, Robert Samuel Newson wrote:
>> Hi,
>>
&
Hi,
I use haproxy (1.8.4) with http/2 support in front of a server that speaks http
1.1. This is working great with one exception. Several http/2 client libraries
are sending PUT requests without sending the Content-Length header (as it' not
strictly needed due to the framing). The http 1.1
Hi,
I think the "cert bundle" feature from 1.7 is broken in 1.8-rc1. My exact
config works with 1.7 but says this for 1.8-rc1;
unable to stat SSL certificate from file '/path/to/foo.pem': No such file or
directory.
That is, it's attempting to load foo.pem, not foo.pem.rsa or foo.pem.ecdsa
On 11 Mar 2016, at 22:43, Willy Tarreau <w...@1wt.eu> wrote:
>
> Robert,
>
> On Fri, Mar 11, 2016 at 10:36:14PM +0000, Robert Samuel Newson wrote:
>> yep, I bound everything but I still get warnings. There's a bug that might be
>> related where binding stats doesn'
ok, I'll try that, and looking forward to a 1.6.4, quite a few good fixes since
1.6.3.
B.
> On 11 Mar 2016, at 22:39, Cyril Bonté <cyril.bo...@free.fr> wrote:
>
> Hi,
>
> Le 11/03/2016 23:36, Robert Samuel Newson a écrit :
>> yep, I bound everything but I still
;> Individual frontends can be set to a specific thread with bind-process (or
>>>> for SSL a frontend specifically for SSL termination can be made). If that
>>>> is the issue your seeing and you want more examples in that direction let
>>>> me know what
Hi,
I'm using haproxy 1.6.3 and think I've uncovered an issue.
I use the stick table feature and as you can see from below, items appear and
disappear randomly, these samples were taken less than a second apart.
Obviously the items in the middle have at least 56 seconds remaining before
tly, it resume the Lua
> code, but immediately.
>
> I join anothe fix. Can you test it ?
>
> Thierry
>
>
> On Sat, 20 Feb 2016 15:54:49 +
> Robert Samuel Newson <rnew...@apache.org> wrote:
>
>> with those changes, and altering my sleep to 1200;
>&
;
> I add Thierry to the discussion (see below for the details).
>
> Le 19/02/2016 20:15, Robert Samuel Newson a écrit :
>> Hi,
>>
>> I think I've found a bug in core.msleep (and core.sleep);
>>
>> foo.lua;
>>
>> core.register_service("f
Hi,
I think I've found a bug in core.msleep (and core.sleep);
foo.lua;
core.register_service("foo", "http", function(applet)
core.msleep(1)
local body = "hello"
applet:set_status(200)
applet:add_header("Content-Length", string.len(body))
applet:start_response()
applet:send(body)
Hi,
I believe I’ve found a bug in HAProxy 1.6.3. If both the resolvers feature and
the seamless reload/state saving feature are both used, it seems that the
backends are considered permanently unreachable.
Here’s my config;
global
stats socket u...@haproxy.sock level admin
defaults
the attached path ?
Thierry FOURNIER
On Sat, 25 Apr 2015 09:32:33 +0200
Thierry FOURNIER tfourn...@haproxy.com wrote:
Hi,
Thank you for the bug repport. I reproduce it, and it was a real bug.
I look for this later.
Thierry
On Thu, 23 Apr 2015 22:42:25 +0100
Robert Samuel Newson
Hi All,
I’m playing with the new set-path feature and encountered a bug. I’m using
1.6-dev1 plus all the patches up to Apr 22nd, I think we’re all clear that
set-path was not working at all in 1.6-dev1 itself. It does now work but not in
all situations I’d expect.
My config is below. I do nc
17 matches
Mail list logo
