On Tue, Nov 13, 2018 at 07:48:38AM +0100, Aleksandar Lazic wrote:
> Hi Fred.
>
> Sorry to be picky but I still think that there is some missing text in the
> documentation, as mentioned before.
>
> http://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=06f5b6435ba99b7a6a034d27b56192e16249f6f0
>
>
Hi Fred.
Sorry to be picky but I still think that there is some missing text in the
documentation, as mentioned before.
http://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=06f5b6435ba99b7a6a034d27b56192e16249f6f0
MINOR: doc: Add information about "early-hint" http-request action.
As I could b
Am 12.11.2018 um 23:31 schrieb Willy Tarreau:
> On Mon, Nov 12, 2018 at 10:52:41PM +0100, Aleksandar Lazic wrote:
>> Oh wow this is really a good time to get the hands dirty as QUIC is a major
>> design change in HTTP, IMHO.
>
> Some first approaches were already attempted about one year ago alrea
On Mon, Nov 12, 2018 at 10:52:41PM +0100, Aleksandar Lazic wrote:
> Oh wow this is really a good time to get the hands dirty as QUIC is a major
> design change in HTTP, IMHO.
Some first approaches were already attempted about one year ago already,
to avoid being later in the party. But just like w
Hi Willy.
Am 12.11.2018 um 21:01 schrieb Willy Tarreau:
> On Mon, Nov 12, 2018 at 07:42:21PM +0100, Aleksandar Lazic wrote:
>> Even I agree with you to the point that HAProxy should be able to handle this
>> next upcomming/available technology, I'm not sure if it's really a benefit
>> for us, the
Hi Willy.
Am 12.11.2018 um 21:14 schrieb Willy Tarreau:
> Hi Aleks,
>
> On Mon, Nov 12, 2018 at 06:00:25PM +0100, Aleksandar Lazic wrote:
>> Hi Fred.
>>
>> Am 12.11.2018 um 15:38 schrieb Frederic Lecaille:
>>> Hello,
>>>
>>> Here is a little series of patches to implement a new http-request
>>> a
Hi Aleks,
On Mon, Nov 12, 2018 at 06:00:25PM +0100, Aleksandar Lazic wrote:
> Hi Fred.
>
> Am 12.11.2018 um 15:38 schrieb Frederic Lecaille:
> > Hello,
> >
> > Here is a little series of patches to implement a new http-request
> > action named "early-hint" to add HTTP 103 responses prior to any
On Mon, Nov 12, 2018 at 03:38:28PM +0100, Frederic Lecaille wrote:
> Hello,
>
> Here is a little series of patches to implement a new http-request
> action named "early-hint" to add HTTP 103 responses prior to any other
> response with headers whose values are defined by log-format rules, as
> thi
On Mon, Nov 12, 2018 at 07:42:21PM +0100, Aleksandar Lazic wrote:
> Even I agree with you to the point that HAProxy should be able to handle this
> next upcomming/available technology, I'm not sure if it's really a benefit
> for us, the enduser.
Hey, why do you guys imagine we're suffering that mu
Hi Manu.
Even I agree with you to the point that HAProxy should be able to handle this
next upcomming/available technology, I'm not sure if it's really a benefit for
us, the enduser.
The future will show it :-)
As I don't want to bother all members on the list with this topic, let's
discuss i
On Mon, Nov 12, 2018 at 04:25:19PM +, David CARLIER wrote:
> Sorry, bas patch... Here the correct one. Regards.
Merged, thank you David.
Willy
Hi Aleks,
> Le 12 nov. 2018 à 18:02, Aleksandar Lazic a écrit :
>
> Hi Manu.
>
> Am 12.11.2018 um 16:19 schrieb Emmanuel Hocdet:
>>
>> Hi,
>>
>> The primary (major) step should be to deal with QUIC transport (over UDP).
>> At the same level as TCP for haproxy?
>> Willy should already have a
Hi Manu.
Am 12.11.2018 um 16:19 schrieb Emmanuel Hocdet:
>
> Hi,
>
> The primary (major) step should be to deal with QUIC transport (over UDP).
> At the same level as TCP for haproxy?
> Willy should already have a little idea on it ;-)
Is then the conclusion for that that haproxy will be able t
Hi Fred.
Am 12.11.2018 um 15:38 schrieb Frederic Lecaille:
> Hello,
>
> Here is a little series of patches to implement a new http-request
> action named "early-hint" to add HTTP 103 responses prior to any other
> response with headers whose values are defined by log-format rules, as
> this is do
The correct patch is in the second message, in case it was missed :-)
Thanks.
Regards.
On Mon, 12 Nov 2018 at 16:28, David CARLIER wrote:
>
> No sorry that was a bad patch, I thought earlier DragonFlyBSD did not
> support but in fact it does.
> On Mon, 12 Nov 2018 at 16:25, Willy TARREAU wrote:
No sorry that was a bad patch, I thought earlier DragonFlyBSD did not
support but in fact it does.
On Mon, 12 Nov 2018 at 16:25, Willy TARREAU wrote:
>
> Hi David,
>
> On Mon, Nov 12, 2018 at 04:16:17PM +, David CARLIER wrote:
> > Subject: [PATCH] BUILD/MEDIUM: DragonFlyBSD build fix
> >
> > T
Hi David,
On Mon, Nov 12, 2018 at 04:16:17PM +, David CARLIER wrote:
> Subject: [PATCH] BUILD/MEDIUM: DragonFlyBSD build fix
>
> This platform does not have particular build on its own, so it
> just uses historically the FreeBSD's. Only it does not support
> the thread/cpu binding.
Is it onl
Sorry, bas patch... Here the correct one. Regards.
On Mon, 12 Nov 2018 at 16:16, David CARLIER wrote:
>
> Hi,
>
> Here a little patch proposal to fix this plarticular platform build.
>
> Cheers.
From e16a4199362748b2492c89e9693e845df28a2eb4 Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Mon,
Hi,
Here a little patch proposal to fix this plarticular platform build.
Cheers.
From 3155cfe8230a1adc6f4878c038474ec9d2aadbc3 Mon Sep 17 00:00:00 2001
From: David Carlier
Date: Mon, 12 Nov 2018 16:11:14 +
Subject: [PATCH] BUILD/MEDIUM: DragonFlyBSD build fix
This platform does not have par
Hi,
The primary (major) step should be to deal with QUIC transport (over UDP).
At the same level as TCP for haproxy?
Willy should already have a little idea on it ;-)
++
Manu
> Le 11 nov. 2018 à 20:38, Aleksandar Lazic a écrit :
>
> Hi.
>
> FYI.
>
> Oh no, that was quite fast after HTTP/2
Hello,
Here is a little series of patches to implement a new http-request
action named "early-hint" to add HTTP 103 responses prior to any other
response with headers whose values are defined by log-format rules, as
this is done with "(add|del)-header" action.
Regards,
Fred.
>From 1780ac43b7d
21 matches
Mail list logo
