Hello!
I see a strange behaviour of the DNS resolution on version 2.0.9 and
2.0.10, but I do not know since when this happens.
On Ubuntu 18.04, I set up haproxy to use the local DNS service provided
by systemd.
Actually I see that haproxy tries to resolve the names every second.
The
On Wed, Nov 27, 2019 at 08:21:44AM +0100, Julien Pivotto wrote:
> On 27 Nov 04:00, Willy Tarreau wrote:
> > Hi guys,
> >
> > Regarding Lua, it is among the packages which don't move fast and which
> > present very little long-term risk, so it can very well be included as
> > a static dependency
On 27 Nov 04:00, Willy Tarreau wrote:
> Hi guys,
>
> Regarding Lua, it is among the packages which don't move fast and which
> present very little long-term risk, so it can very well be included as
> a static dependency if not supported in certain distros. I've already
> been wondering whether or
ср, 27 нояб. 2019 г. в 05:02, Lukas Tribus :
> Hello,
>
> On Tue, Nov 26, 2019 at 10:50 PM Илья Шипицин
> wrote:
> >
> > Hello,
> >
> > I resolved `CRYPTO_set_id_callback', `ERR_remove_state',
> `SSL_CTX_set_ecdh_auto' issues.
> >
> >
> > the following two will be addressed later:
Hi,
On Sun, Nov 24, 2019 at 09:59:50PM +0900, flamese...@yahoo.co.jp wrote:
> Just wondering why not single git repository and use branches for different
> versions?
> Instead:
> haproxy-1.8.githaproxy-1.9.githaproxy-2.0.git
> use git://git.haproxy.com/haproxy.gitanddevelop branch for current
>
On Wed, Nov 27, 2019 at 01:02:25AM +0100, Lukas Tribus wrote:
> Hello,
>
> On Tue, Nov 26, 2019 at 10:50 PM ??? wrote:
> >
> > Hello,
> >
> > I resolved `CRYPTO_set_id_callback', `ERR_remove_state',
> > `SSL_CTX_set_ecdh_auto' issues.
> >
> >
> > the following two will be addressed
On Wed, Nov 27, 2019 at 12:31:48AM +0100, Lukas Tribus wrote:
> That said, I'm not sure this was really the intention of the change in
> question (commit 531b83e03 "MINOR: h1: Reject requests if the
> authority does not match the header host"). Christopher?
I'm pretty sure it was not intended and
Hi guys,
On Tue, Nov 26, 2019 at 09:01:17PM +0100, William Lallemand wrote:
> On Tue, Nov 26, 2019 at 08:33:41PM +0100, Julien Pivotto wrote:
> > Dear HAProxy Community,
> >
> > I have started building HAProxy 2.x packages for CentOS.
> >
> > It includes HAProxy 2.0.10 and 2.1.0.
> >
> > You
Hi Ilya,
On Wed, Nov 27, 2019 at 02:50:18AM +0500, ??? wrote:
> Hello,
>
> I resolved `CRYPTO_set_id_callback', `ERR_remove_state',
> `SSL_CTX_set_ecdh_auto' issues.
Great, thanks!
I'm seeing some minor cosmetic details:
> @@ -5046,7 +5046,9 @@ int ssl_sock_prepare_ctx(struct
Hello Julien,
On Wed, Nov 27, 2019 at 12:47 AM Julien Pivotto wrote:
> Yes indeed. I tested too and it works. I indeed tried
> accept-invalid-http-request like in the commit message
> instead of accept-invalid-http-response.
>
> My concern with the workaround is that there might be huge
> side
Hello,
On Tue, Nov 26, 2019 at 10:50 PM Илья Шипицин wrote:
>
> Hello,
>
> I resolved `CRYPTO_set_id_callback', `ERR_remove_state',
> `SSL_CTX_set_ecdh_auto' issues.
>
>
> the following two will be addressed later: `X509_get_notBefore',
> `X509_get_notAfter'
I'm not sure if matching
On 27 Nov 00:39, Lukas Tribus wrote:
> On Wed, Nov 27, 2019 at 12:36 AM Julien Pivotto
> wrote:
> >
> > On 27 Nov 00:31, Lukas Tribus wrote:
> > > Hello Julien,
> > >
> > >
> > >
> > > On Wed, Nov 27, 2019 at 12:21 AM Julien Pivotto
> > > wrote:
> > > > Haproxy 2.1 blocks a response with PH--
On Wed, Nov 27, 2019 at 12:36 AM Julien Pivotto wrote:
>
> On 27 Nov 00:31, Lukas Tribus wrote:
> > Hello Julien,
> >
> >
> >
> > On Wed, Nov 27, 2019 at 12:21 AM Julien Pivotto
> > wrote:
> > > Haproxy 2.1 blocks a response with PH-- if the response has a Host header.
> >
> > A Host header
On 27 Nov 00:31, Lukas Tribus wrote:
> Hello Julien,
>
>
>
> On Wed, Nov 27, 2019 at 12:21 AM Julien Pivotto
> wrote:
> > Haproxy 2.1 blocks a response with PH-- if the response has a Host header.
>
> A Host header belongs to the request, not the response. Haproxy 2.1 is
> more strict in
Hello Julien,
On Wed, Nov 27, 2019 at 12:21 AM Julien Pivotto wrote:
> Haproxy 2.1 blocks a response with PH-- if the response has a Host header.
A Host header belongs to the request, not the response. Haproxy 2.1 is
more strict in that regard. You can configure "option
Hello
Haproxy 2.1 blocks a response with PH-- if the response has a Host header.
Haproxy config:
frontend default
bind 127.0.0.1:8443
use_backend default
log stdout format raw local0
mode http
option httplog
backend default
mode http
Ilya,
I can't comment about the patch itself, but wanted to comment about the
commit message.
Am 26.11.19 um 22:50 schrieb Илья Шипицин:
> Subject: [PATCH] CLEANUP: partially resolve #367
I believe this should be the 'BUILD' tag instead of CLEANUP. And I also
recommend to give a more
Hello,
I resolved `CRYPTO_set_id_callback', `ERR_remove_state',
`SSL_CTX_set_ecdh_auto' issues.
the following two will be addressed later: `X509_get_notBefore',
`X509_get_notAfter'
Cheers,
Ilya Shipitsin
From 158e07f29cbd40c7cd159330ffd748cb1b926647 Mon Sep 17 00:00:00 2001
From: Ilya
ср, 27 нояб. 2019 г. в 01:10, Russell Eason :
> Hello,
>
> Fedora upstream added it
> https://src.fedoraproject.org/rpms/haproxy/c/45c57ba71174f308a5f59569bac0598bb31ef767
> , and can be seen as far back as F24 here
> https://src.fedoraproject.org/rpms/haproxy/blob/f24/f/haproxy.spec . LUA
>
ср, 27 нояб. 2019 г. в 01:03, William Lallemand :
> On Tue, Nov 26, 2019 at 08:33:41PM +0100, Julien Pivotto wrote:
> > Dear HAProxy Community,
> >
> > I have started building HAProxy 2.x packages for CentOS.
> >
> > It includes HAProxy 2.0.10 and 2.1.0.
> >
> > You can find them here:
> >
Hello,
Fedora upstream added it
https://src.fedoraproject.org/rpms/haproxy/c/45c57ba71174f308a5f59569bac0598bb31ef767
, and can be seen as far back as F24 here
https://src.fedoraproject.org/rpms/haproxy/blob/f24/f/haproxy.spec . LUA
support is in the RHEL 8 version of HAProxy, but not in 7
On Tue, Nov 26, 2019 at 08:33:41PM +0100, Julien Pivotto wrote:
> Dear HAProxy Community,
>
> I have started building HAProxy 2.x packages for CentOS.
>
> It includes HAProxy 2.0.10 and 2.1.0.
>
> You can find them here:
> https://copr.fedorainfracloud.org/coprs/roidelapluie/haproxy/
>
>
On 27 Nov 00:51, Илья Шипицин wrote:
> thank for the rpm
>
> it was faster than I did ))
>
> any plans to add Lua ?
Hello,
It is not in the upstream spec file that I use, and I personnaly do not
use lua yet. If there is interest I can have a look at that.
>
> ср, 27 нояб. 2019 г. в 00:36,
thank for the rpm
it was faster than I did ))
any plans to add Lua ?
ср, 27 нояб. 2019 г. в 00:36, Julien Pivotto :
> Dear HAProxy Community,
>
> I have started building HAProxy 2.x packages for CentOS.
>
> It includes HAProxy 2.0.10 and 2.1.0.
>
> You can find them here:
>
Dear HAProxy Community,
I have started building HAProxy 2.x packages for CentOS.
It includes HAProxy 2.0.10 and 2.1.0.
You can find them here:
https://copr.fedorainfracloud.org/coprs/roidelapluie/haproxy/
https://github.com/roidelapluie/haproxy-rpm
which is based on
On Tue, Nov 26, 2019 at 08:28:51AM -0600, Dave Chiluk wrote:
> Ubuntu 16.04 is on 1.6 which is bug-fix "supported" till 2021. It's
> probably fine to deprecate next year.
> Ubuntu 18.04 is on 1.8 which is bug-fix "supported" till 2023.
>
> Debian has 1.8 in their stable and 2.0.9 in unstable,
Ubuntu 16.04 is on 1.6 which is bug-fix "supported" till 2021. It's
probably fine to deprecate next year.
Ubuntu 18.04 is on 1.8 which is bug-fix "supported" till 2023.
Debian has 1.8 in their stable and 2.0.9 in unstable, but I'm not as
familiar with their release cycles.
RHEL/Centos 7 haproxy
Hi Vincent,
On Tue, Nov 26, 2019 at 01:33:30PM +0100, Vincent Bernat wrote:
> ? 25 octobre 2019 11:27 +02, Willy Tarreau :
>
> > Now I'm wondering, is anyone interested in this branch to still be
> > maintained ? Should I emit a new release with a few pending fixes
> > just to flush the pipe
❦ 25 octobre 2019 11:27 +02, Willy Tarreau :
> Now I'm wondering, is anyone interested in this branch to still be
> maintained ? Should I emit a new release with a few pending fixes
> just to flush the pipe and pursue its "critical fixes only" status a
> bit further, or should we simply declare
we were decoding all substring and then parsing; this could lead to
consider & and = in decoding result as delimiters where it should not.
this patch reverses the order by first parsing and then decoding each key
and value separately.
we also stop parsing after number sign (#).
This patch should
On Mon, Nov 25, 2019 at 10:30:55AM +0100, Christopher Faulet wrote:
> First, a key without value is not properly handled. You must not try to
> parse the value, otherwise the following parameter is read as value. For
> instance "/metrics?no-maint=server".
oh good catch fixed.
> Then, if empty
Hi William,
> Le 22 nov. 2019 à 17:34, William Lallemand a écrit :
>
> Hi Manu,
>
> I have a few questions/remarks below:
>
>> Subject: [PATCH 1/3] MINOR: ssl: deduplicate ca-file
>> [...]
>>
>> +static int ssl_store_load_locations_file(X509_STORE **store_ptr, char *path)
>> +{
>> +
32 matches
Mail list logo
