Good Morning Lukas,
Thank you!
This was indeed the change which was necessary.
Removed the ssl_fc_sni part in my ACLs, reactivated h2 and I’m back on track.
Cheers (from a happy http2 user),
Chris
> Am 11.12.2017 um 23:48 schrieb Lukas Tribus :
>
> Hell Chris,
>
>
>
Hi
There is a simpler solution with delegate.
I have run a squid on localhost 127.0.0.1:3128
I have run delegate with PROXY module
delegate9.9.13$ src/delegated -f -vv -P127.0.0.1:8081
PROXY=127.0.0.1:3128
and now the swiss army knife curl was the haproxy simulator.
echo 'GET
> > > Did you try launching a new haproxy process with the -sf option, without
> > > using the master-worker?
> >
> > Yes, and that also failed with the same "cannot bind" error.
> Without "expose-fd listeners" I suppose?
That is correct.
> Okay, so it looks like that the unbinding with SIGTOUT
On Mon, Dec 11, 2017 at 11:03:52PM +, Anthony Via wrote:
> > Did you try the seamless reload using -x without the master-worker?
>
> I was looking into the "-x" option and it looks like simply adding "expose-fd
> listeners" to my stats socket has fixed this issue for me. Sending SIGUSR2 to
>
> Did you try the seamless reload using -x without the master-worker?
I was looking into the "-x" option and it looks like simply adding "expose-fd
listeners" to my stats socket has fixed this issue for me. Sending SIGUSR2 to
the master process now works as expected. Is that option required for
Hell Chris,
2017-12-11 20:04 GMT+01:00 Christian Bönning :
> Hi,
>
> I recently switched from nginx to haproxy 1.8 for SSL termination and load
> balancing in front of my application but saw an odd behaviour with "alpn
> h2,http/1.1" enabled on my frontend.
>
>
On Sat, Dec 9, 2017 at 10:18 PM, Willy Tarreau wrote:
> On Sat, Dec 09, 2017 at 10:10:25AM +0100, Pavlos Parissis wrote:
>> On 09/12/2017 05:01 ?u, Christopher Lane wrote:
>> > It is plausible/expected that my version upgrade performance goes like
>> > (about 4K connections,
>> >
Hi.
-- Originalnachricht --
Von: "Moemen MHEDHBI"
An: "Gbg" ; haproxy@formilux.org
Gesendet: 11.12.2017 18:45:16
Betreff: Re: Use haproxy 1.8.x to balance web applications only
reachable through Internet proxy
On 11/12/2017 17:21, Gbg wrote:
Hi,
I recently switched from nginx to haproxy 1.8 for SSL termination and load
balancing in front of my application but saw an odd behaviour with "alpn
h2,http/1.1" enabled on my frontend.
I'm running a single haproxy instance in front of my applications switching
between them based on
On 11/12/2017 17:21, Gbg wrote:
> Hello Moemen,
>
> unless I got this wrong this isn't the setup I search for. I don't
> need haproxy to *be* a proxy but rather *use* a proxy while serving
> content over http as a reverse proxy
>
> Perhaps I should have given the thread this name
I get your
Hello Moemen,
unless I got this wrong this isn't the setup I search for. I don't need haproxy
to *be* a proxy but rather *use* a proxy while serving content over http as a
reverse proxy
Perhaps I should have given the thread this name
Am 11. Dezember 2017 16:56:12 MEZ schrieb Moemen MHEDHBI
On 11/12/2017 15:02, Gbg wrote:
> I need to contact applications through a socks or http proxy.
>
> My current setup looks like this but only works when the Computer
> haproxy runs on has direct Internet connection (which is not the case
> in our datacenter, I tried this at home)
>
> frontend
Hi Andreas,
I got this really side tracked, my apology. Let me take a look at that
this evening again. Some corps need to be unburied.
I'm afraid the patch, as is, will break compatibility with other version
of the CIP protocol, I'd like haproxy to support both of them.
Cheers,
Bertrand
On
I need to contact applications through a socks or http proxy.
My current setup looks like this but only works when the Computer haproxy runs
on has direct Internet connection (which is not the case in our datacenter, I
tried this at home)
frontend main
bind *:8000
acl is_extweb1 path_beg -i
Hi Lukas,
On Mon, Dec 11, 2017 at 11:54:07AM +0100, Lukas Tribus wrote:
> Hello Willy,
>
>
>
> 2017-12-07 19:55 GMT+01:00 Willy Tarreau :
> > Guys,
> >
> > just to warn you, there's currently an issue affecting HTTP/2 with POST
> > payloads to "slow" servers.
>
> Ok, the POST
Hello Willy,
2017-12-07 19:55 GMT+01:00 Willy Tarreau :
> Guys,
>
> just to warn you, there's currently an issue affecting HTTP/2 with POST
> payloads to "slow" servers.
Ok, the POST issue is obviously more important, but just to provide a
complete picture we also have those 2
16 matches
Mail list logo