Hi.
Cloudflare have announced that their edge serves are able to handle HTTP/3 in a
draft version, please can anyone from HAProxy tell us what you plans are about
HTTP/3, thanks.
https://blog.cloudflare.com/http3-the-past-present-and-future/
[https://blog.cloudflare.com/http3-the-past-pres
Hi,
HAProxy 1.9.11 was released on 2019/09/27. It added 33 new commits
after version 1.9.10.
This release fixes several issues in the H2 multiplexer, among which 2 major
bugs about the way received frames are handled on the error path. The first one
comes from the first age of the H2 multiplexer.
Hi,
HAProxy 2.0.7 was released on 2019/09/27. It added 20 new commits
after version 2.0.6.
This release fixes several issues in the H2 multiplexer, among which 2 major
bugs about the way received frames are handled on the error path. The first one
comes from the first age of the H2 multiplexer. D
> Le 27 sept. 2019 à 12:23, Geoff Simmons a écrit :
>
> On 9/26/19 19:27, Emmanuel Hocdet wrote:
>
>>> And I wonder if there are situations in which someone will want to
>>> specifically choose one source of truth for authority over the other.
>>> Suppose an incoming connection uses TLS with a
*From:* Marco Colli [mailto:collimarc...@gmail.com]
*Sent:* Friday, September 27, 2019, 07:21 EDT
*To:* HAProxy
*Subject:* How to wait some time before retry?
Still have this issue and I cannot find a solution. It would b
I have already set "timeout connect" to 10s, but it doesn't work. I think
because the connection is *immediately rejected* by the OS (Ubuntu) if
there isn't any process listening on it (i.e. during the Puma server
restart).
On Fri, Sep 27, 2019 at 2:11 PM Lukas Tribus wrote:
> Ciao Marco,
>
>
>
Ciao Marco,
On Fri, Sep 27, 2019 at 1:21 PM Marco Colli wrote:
>
> Still have this issue and I cannot find a solution. It would be great to have
> an option "wait time before retry" in the next versions of HAProxy (instead
> of the fixed value of 1 sec).
Why not raise "timeout connect" to 10
Still have this issue and I cannot find a solution. It would be great to
have an option "wait time before retry" in the next versions of HAProxy
(instead of the fixed value of 1 sec).
On Mon, Sep 16, 2019 at 2:03 PM Marco Colli wrote:
> Hello!
>
> I have a question about HAProxy configuration. M
On 9/26/19 19:27, Emmanuel Hocdet wrote:
>
>>>
>>> Proposal reworking after playing with « authority » and look at how « src
>>> »/« dst » are working.
>>>
>>> Authority » can come from transport layer (TLS), ProxyV2 TLV or «
>>> set-authority ».
>>> « src/dst » is set from transport layer (TCP)
Hi,
I'm on 1.8.21 and have a webapp that uses websockets.
The application works, but the app complains very quickly that the
connection to the server has been lost.
On the second line we get "sD--" Which is:
sD The server did not send nor acknowledge any data for as long as
the "timeout serve
Le 17/09/2019 à 11:11, Christopher Faulet a écrit :
Le 16/09/2019 à 03:40, Kevin Zhu a écrit :
Sorry Crhistopher, have you look at this mail ?😁
On Mon, 2 Sep 2019 at 16:11, Kevin Zhu mailto:ip0...@gmail.com>> wrote:
Hi Christopher
SPOE engine-id is all same when nbproc is more than
11 matches
Mail list logo
