Thank you Willy!
A
On Wed, Sep 9, 2020 at 1:31 PM Willy Tarreau wrote:
> On Wed, Sep 09, 2020 at 07:20:17PM +0200, Willy Tarreau wrote:
> > Feel free to pick this patch if that helps for your builds, I'm going
> > to backport it to 2.2 once all platforms are happy.
>
> All builds are OK now, th
Correct.. this is arm based on my side as well.
Sent from my Pixel 3XL
On Tue, Sep 8, 2020, 5:47 PM Vincent Bernat wrote:
> ❦ 8 septembre 2020 16:13 -04, Alex Evonosky:
>
> > Just compiling 2.2.3 and getting this reference:
> >
> >
> > /haproxy-2.2.3/src/thr
Hello Haproxy group-
Just compiling 2.2.3 and getting this reference:
/haproxy-2.2.3/src/thread.c:212: undefined reference to `_Unwind_Find_FDE'
Is there a new lib thats required?
Thank you!
Thank you Willy. That did it!
Great work!
Sent from my Pixel 3XL
On Mon, Dec 16, 2019, 11:50 PM Willy Tarreau wrote:
> Hello Alex,
>
> On Mon, Dec 16, 2019 at 01:22:42PM -0500, Alex Evonosky wrote:
> > Hello Haproxy group-
> >
> > migrating from haproxy
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
after compiling the new 2.0.1, it seems the HTTP2 issue *we were seeing* on
2.0 but not on 1.9.8 are fixed.
Thank you.
On Thu, Jun 27, 2019 at 7:19 AM Aleksandar Lazic wrote:
> Am 26.06.2019 um 19:28 schrieb Christopher Faulet:
> > Hi,
> >
> > HAProxy 2.0.1 was released on 2019/06/26. It added
Jeff
>
>
> On 20/05/2019 17:48, Alex Evonosky wrote:
>
> example:
>
> pod1:
>
> primary: 1.1.1.2
> secondary: 1.1.1.3
> virtual: 1.1.1.1
>
>
> pod2:
>
> primary: 1.1.1.5
> secondary: 1.1.1.6
> virtual: 1.1.1.4
>
>
> The mechanism to utiliz
> Sorry if my questions are overly basic. I'm just trying to get a grip on
> what this means and how to do it.
>
> Jeff
>
>
> On 20/05/2019 17:12, Alex Evonosky wrote:
>
> Jeff-
>
> ViP - Virtual IP. this is a shared IP between nodes. One node is primary
&g
gt; Anecdotally, I noticed a while back that Google and others, which used to
> have DNS resolutions from one name to multiple IP's, now resolve to a
> single IP.
>
> Jeff Abrahamson
> http://p27.eu/jeff/
> http://transport-nantes.com/
>
>
> On 20/05/2019 15:04, Al
You could make it a bit more agile and scale it:
you can run them in "pods", such as two haproxy instances running
keepalived between them and use the ViP IP as the DNS record, so if an
HAproxy instance was to die, the alternate HAproxy instance can take over.
Set more pods up and use DNS round ro
Tim-
I can speak from a production point of view that we had HAproxy on the 1.6
branch inside docker containers for mesos load balancing with pretty much
the same requirements as you spoke of. After compiling Haproxy to the 1.8x
branch the same config worked without issues.
-Alex
On Mon, Jul 1
Congratulations!
On Mon, Nov 27, 2017 at 8:41 AM, Arnall wrote:
> Le 26/11/2017 à 19:57, Willy Tarreau a écrit :
>
>> Hi all,
>>
>> After one year of intense development and almost one month of debugging,
>> polishing, and cross-review work trying to prevent our respective
>> coworkers
>> from w
12 matches
Mail list logo
