On Tue, Dec 17, 2019 at 08:41:55AM +0100, Julien Pivotto wrote:
> On 17 Dec 06:58, Willy Tarreau wrote:
> > On Tue, Dec 17, 2019 at 06:08:56AM +0100, Willy Tarreau wrote:
> > > But now I'm starting to suspect that most of the problem comes from the
> > > fact that people who used to rely on regex i
On 17 Dec 06:58, Willy Tarreau wrote:
> On Tue, Dec 17, 2019 at 06:08:56AM +0100, Willy Tarreau wrote:
> > But now I'm starting to suspect that most of the problem comes from the
> > fact that people who used to rely on regex in the past will not as easily
> > perform their rewrites using set-path
On Tue, Dec 17, 2019 at 06:58:11AM +0100, Willy Tarreau wrote:
> On Tue, Dec 17, 2019 at 06:08:56AM +0100, Willy Tarreau wrote:
> > But now I'm starting to suspect that most of the problem comes from the
> > fact that people who used to rely on regex in the past will not as easily
> > perform their
On Tue, Dec 17, 2019 at 06:08:56AM +0100, Willy Tarreau wrote:
> But now I'm starting to suspect that most of the problem comes from the
> fact that people who used to rely on regex in the past will not as easily
> perform their rewrites using set-path as they would using a replace rule
> which is
Hi guys,
On Mon, Dec 16, 2019 at 11:01:19PM +0100, Cyril Bonté wrote:
> Hi Willy,
>
> Le 16/12/2019 à 22:06, Artur a écrit :
> > > > [...]
> > > > URLs like https://q.d/PPDSlide/testfile are correctly rewritten to
> > > > https://q.d/p3/PPDSlide/testfile and forwarded to the backend.
> > > >
> >
Hello Alex,
On Mon, Dec 16, 2019 at 01:22:42PM -0500, Alex Evonosky wrote:
> Hello Haproxy group-
>
> migrating from haproxy 2.0 to 2.1 and noticed some directives changed:
>
> === 2.0.10 ===
>
> capture request header origin len 128
> http-response add-header Access-Control-Allow-Origin %[capt
Hi Joao,
On Sat, Dec 14, 2019 at 11:30 PM Joao Morais wrote:
>
>
> > Em 13 de dez de 2019, à(s) 10:09, Christopher Faulet <
> cfau...@haproxy.com> escreveu:
> >
> > Le 10/12/2019 à 05:24, Igor Cicimov a écrit :
> >>
> >> Testing with Haproxy 2.0.10 but same result with 1.8.23. The versions
> of
Hi,
On Tue, Dec 17, 2019 at 2:55 AM Olivier D wrote:
> Hello,
>
> I found what was wrong : I was using "load-server-state-from-file" and
> previous config file was using port 80 as server port.
> It seems using this instruction loads previous server state but also
> previous srv_port.
> Is this
Hi Willy,
Le 16/12/2019 à 22:06, Artur a écrit :
[...]
URLs like https://q.d/PPDSlide/testfile are correctly rewritten to
https://q.d/p3/PPDSlide/testfile and forwarded to the backend.
Once I switched to 2.1.1, haproxy no longer rewrites the URI and the
URIs remains unchanged while forwarded to
On 16 Dec 15:00, Ryan O'Hara wrote:
> On Tue, Nov 26, 2019 at 2:40 PM Russell Eason wrote:
>
> > 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.fedorapr
Hello,
While checking for haproxy 2.1 package for Debian Stretch on
https://haproxy.debian.net/, I saw it wasn't available (yet ?).
Do you plan to build haproxy deb packages for this version of Debian,
it's still supported as oldstable for now ?
--
Best regards,
Artur
On Tue, Nov 26, 2019 at 9:20 PM Willy Tarreau wrote:
>
> Indeed that looks good. We'll need to include Ryan in this discussion,
> he's the maintainer of the official RPMs for RHEL. I'm purposely not CCing
> him as I know he's very busy this week, but I sense that we're starting to
> see the light
вт, 17 дек. 2019 г. в 00:55, Rosen Penev :
> On Mon, Dec 16, 2019 at 10:21 AM Илья Шипицин
> wrote:
> >
> >
> >
> > пн, 16 дек. 2019 г. в 22:40, Rosen Penev :
> >>
> >> On Mon, Dec 16, 2019 at 4:49 AM Lukas Tribus wrote:
> >> >
> >> > Hello Rosen,
> >> >
> >> > > пн, 16 дек. 2019 г. в 12:07, Ros
Hello Cyril,
Thanks a lot for the confirmation.
Le 16/12/2019 à 20:20, Cyril Bonté a écrit :
> Hi Artur,
>
> Le 16/12/2019 à 19:06, Artur a écrit :
>> Hello,
>>
>> This is an extract of my frontend configuration working perfectly on
>> 2.0.11.
>>
>> frontend wwws
>> bind 0.0.0.0:443 ssl
On Tue, Nov 26, 2019 at 2:40 PM Russell Eason wrote:
> 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
On Mon, Dec 16, 2019 at 10:21 AM Илья Шипицин wrote:
>
>
>
> пн, 16 дек. 2019 г. в 22:40, Rosen Penev :
>>
>> On Mon, Dec 16, 2019 at 4:49 AM Lukas Tribus wrote:
>> >
>> > Hello Rosen,
>> >
>> > > пн, 16 дек. 2019 г. в 12:07, Rosen Penev :
>> > >>
>> > >> LIBRESSL_VERSION_NUMBER evaluates to 0 un
On Mon, Dec 16, 2019 at 10:09 AM Lukas Tribus wrote:
>
> On Mon, 16 Dec 2019 at 19:00, Илья Шипицин wrote:
> >
> >
> >
> > пн, 16 дек. 2019 г. в 22:42, Rosen Penev :
> >>
> >> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
> >> always true. Check for the define before
Hi Artur,
Le 16/12/2019 à 19:06, Artur a écrit :
Hello,
This is an extract of my frontend configuration working perfectly on 2.0.11.
frontend wwws
bind 0.0.0.0:443 ssl crt /etc/haproxy/ssl/server.pem alpn
h2,http/1.1
mode http
acl is_dev_qd hdr(host) -i dev.q.d dev.q
Hello Haproxy group-
migrating from haproxy 2.0 to 2.1 and noticed some directives changed:
=== 2.0.10 ===
capture request header origin len 128
http-response add-header Access-Control-Allow-Origin %[capture.req.hdr(0)]
if { capture.req.hdr(0) -m end aiqwest.com }
http-response add-header Access
пн, 16 дек. 2019 г. в 22:40, Rosen Penev :
> On Mon, Dec 16, 2019 at 4:49 AM Lukas Tribus wrote:
> >
> > Hello Rosen,
> >
> > > пн, 16 дек. 2019 г. в 12:07, Rosen Penev :
> > >>
> > >> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the
> condition
> > >> always true. Check for the d
On Mon, 16 Dec 2019 at 19:00, Илья Шипицин wrote:
>
>
>
> пн, 16 дек. 2019 г. в 22:42, Rosen Penev :
>>
>> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
>> always true. Check for the define before checking it.
>>
>> Signed-off-by: Rosen Penev
>> ---
>> include/common
On Mon, Dec 16, 2019 at 10:00 AM Илья Шипицин wrote:
>
>
>
> пн, 16 дек. 2019 г. в 22:42, Rosen Penev :
>>
>> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
>> always true. Check for the define before checking it.
>>
>> Signed-off-by: Rosen Penev
>> ---
>> include/com
Hello,
This is an extract of my frontend configuration working perfectly on 2.0.11.
frontend wwws
bind 0.0.0.0:443 ssl crt /etc/haproxy/ssl/server.pem alpn
h2,http/1.1
mode http
acl is_dev_qd hdr(host) -i dev.q.d dev.qs.d
acl is_qd hdr(host) -i q.d qs.d www.q.d www
пн, 16 дек. 2019 г. в 22:42, Rosen Penev :
> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
> always true. Check for the define before checking it.
>
> Signed-off-by: Rosen Penev
> ---
> include/common/openssl-compat.h | 2 +-
> 1 file changed, 1 insertion(+), 1 delet
On Mon, Dec 16, 2019 at 4:49 AM Lukas Tribus wrote:
>
> Hello Rosen,
>
> > пн, 16 дек. 2019 г. в 12:07, Rosen Penev :
> >>
> >> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
> >> always true. Check for the define before checking it.
>
> I cannot find this in the openss
LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
always true. Check for the define before checking it.
Signed-off-by: Rosen Penev
---
include/common/openssl-compat.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/common/openssl-compat.h b/in
Hello,
On Mon, 16 Dec 2019 at 09:20, Willy Tarreau wrote:
>
> Hi Lukas,
>
> On Sun, Dec 15, 2019 at 05:23:38PM +0100, Lukas Tribus wrote:
> > Currently this debug converter is only enabled when DEBUG_EXPR is
> > defined at build time (which is different than other debug build
> > options and uncl
Hello,
I found what was wrong : I was using "load-server-state-from-file" and
previous config file was using port 80 as server port.
It seems using this instruction loads previous server state but also
previous srv_port.
Is this an expected behaviour ?
Olivier
Le ven. 13 déc. 2019 à 18:32, Oliv
Hello Rosen,
> пн, 16 дек. 2019 г. в 12:07, Rosen Penev :
>>
>> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
>> always true. Check for the define before checking it.
I cannot find this in the openssl sources, not in master and not in
the 1.1.1 branch. Please clarify
also, BoringSSL fails after applying your patch
https://travis-ci.com/chipitsine/haproxy/jobs/267601286
пн, 16 дек. 2019 г. в 12:07, Rosen Penev :
> LIBRESSL_VERSION_NUMBER evaluates to 0 under OpenSSL, making the condition
> always true. Check for the define before checking it.
>
> Signed-off-b
On Mon, Dec 16, 2019 at 09:30:38AM +0100, Baptiste wrote:
> My 2 cents.
> I personally use a lot this converter, si I'd be more than happy to get it
> available in default built!
OK.
> I think Willy's idea to route its output wherever we want is great too for
> production purpose.
At least the t
On Mon, Dec 16, 2019 at 9:22 AM Willy Tarreau wrote:
> Hi Lukas,
>
> On Sun, Dec 15, 2019 at 05:23:38PM +0100, Lukas Tribus wrote:
> > Currently this debug converter is only enabled when DEBUG_EXPR is
> > defined at build time (which is different than other debug build
> > options and unclear fro
Hi Lukas,
On Sun, Dec 15, 2019 at 05:23:38PM +0100, Lukas Tribus wrote:
> Currently this debug converter is only enabled when DEBUG_EXPR is
> defined at build time (which is different than other debug build
> options and unclear from the documentation).
>
> This moves the patch to the default bui
пн, 16 дек. 2019 г. в 12:47, William Lallemand :
> Hello Rosen,
>
> On Sun, Dec 15, 2019 at 11:04:37PM -0800, Rosen Penev wrote:
> > -#if (OPENSSL_VERSION_NUMBER < 0x1010L) || (LIBRESSL_VERSION_NUMBER
> < 0x2070L)
> > +#if (OPENSSL_VERSION_NUMBER < 0x1010L) || \
> > + (defined(LIBR
34 matches
Mail list logo
