William,
Am 27.08.20 um 18:53 schrieb William Lallemand:
> Sorry for the late reply,
All good, it's not arriving earlier than 2.3 anyway :-)
> On Tue, Aug 18, 2020 at 11:19:05PM +0200, Tim Duesterhus wrote:
>> @@ -875,6 +877,7 @@ static void http_cache_io_handler(struct appctx *appctx)
>> u
Hello Tim,
Sorry for the late reply,
On Tue, Aug 18, 2020 at 11:19:05PM +0200, Tim Duesterhus wrote:
> Before continuing cleaning this up and properly handling both strong and weak
> ETags according to the RFC I'd like to have a first review to see whether I am
> generally on the right track ther
Hello,
asan findings were mixed with reg-tests errors and it was hard to
investigate.
Cheers,
Ilya Shipitcin
From 1fb2b510a2c5b5c7cc0522f8013dcb1474ab5314 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 27 Aug 2020 21:00:09 +0500
Subject: [PATCH] CI: travis-ci: split asan step out of ru
On Thu, Aug 27, 2020 at 05:39:34PM +0200, Tim Düsterhus, WoltLab GmbH wrote:
> Willy and I discussed this in private. My understanding is that this
> issue is caused by an inherent limitation of H2 with regard to head of
> the line blocking.
>
> In simple terms:
>
> If the stuff at the beginning
Hi List,
Am 27.08.20 um 11:45 schrieb Tim Düsterhus, WoltLab GmbH:
>> You can see two h2c connections, one is on the frontend (hence the 'F')
>> and the other one is on the backend. The h2s is the H2 stream, unique to
>> a request (though it comes from a pool, so it will be reused for new
>> strea
Hi ,
I am trying to enable corse with below in my frontend
capture request header origin len 128
http-response add-header Access-Control-Allow-Origin %[capture.req.hdr(0)]
I am not able to see any header set if I try to check using curl
curl --verbose -H "Origin: "example.com" --head example2.c
On Thu, Aug 27, 2020 at 09:19:24PM +0800, Hongyi Zhao wrote:
> On Thu, Aug 27, 2020 at 9:51 AM Willy Tarreau wrote:
> >
> > Hi,
> >
> > On Mon, Aug 17, 2020 at 10:09:36PM +0800, Hongyi Zhao wrote:
> > > Hi,
> > >
> > > Is it possible for the following settings in haproxy:
> > >
> > > A http fronte
Willy,
Thanks for that tip, sounds like a really good idea.
I talked to Pete and he's added it to the list for the next version along with:
Code clean ups, 64 bit values, reading settings from the netsnmp
configuration files, better HAProxy version support and so on...
Malcolm Turnbull
Loadbal
On Thu, Aug 27, 2020 at 9:51 AM Willy Tarreau wrote:
>
> Hi,
>
> On Mon, Aug 17, 2020 at 10:09:36PM +0800, Hongyi Zhao wrote:
> > Hi,
> >
> > Is it possible for the following settings in haproxy:
> >
> > A http frontend listening on the localhost:18887 which uses a backend
> > consisting of severa
On Thu, Aug 27, 2020 at 11:45:13AM +0200, Tim Düsterhus, WoltLab GmbH wrote:
> Willy,
>
> Am 27.08.20 um 10:29 schrieb Willy Tarreau:
> >> I now have the trace results and my HAProxy log where I can correlate
> >> the slow requests using the timestamp and path. Unfortunately the trace
> >> does no
Willy,
Am 27.08.20 um 10:29 schrieb Willy Tarreau:
>> I now have the trace results and my HAProxy log where I can correlate
>> the slow requests using the timestamp and path. Unfortunately the trace
>> does not appear to contain the unique-id of the request.
>
> Sadly, due to the way HPACK works
Hello,
On Thu, 2020-08-27 at 13:33 +0530, Roshan Singh wrote:
> Dear HAProxy Technical Support Team,
>
> REQUEST: HAProxy supports IPv4 Header manipulation for QoS.
>
> ISSUE: I have been trying to pass the ToS value received from client to
> backend server for DSCP. But i can't manipulate DSCP
Hi Tim,
On Thu, Aug 27, 2020 at 10:05:08AM +0200, Tim Düsterhus, WoltLab GmbH wrote:
> My definition of reproducible is "I can write up a list of steps that
> makes the issue happen somewhat reliably".
OK, that's fine by me :-)
> This morning I re-enabled H2 for the backend communication and the
Willy,
Am 26.08.20 um 17:51 schrieb Willy Tarreau
>> As I said: It's not really reproducible.
>
> Yeah but we all have a definition of "not really reproducible". As you
> consider that it doesn't happen in HTTP/1 after only 4 hours, for me
> this means you expect it to usually happen at least onc
On Mon, Aug 24, 2020 at 09:59:25PM +0300, Milen Simeonov wrote:
> I've got an issue after HAProxy 2.0.17 upgrade to 2.2.2
>
>
> ## Detailed description of the problem
>
> The following packages will be upgraded:
> haproxy
> 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need
15 matches
Mail list logo