capture length and redirect

Location: https://www.example.com/T Connection: close $ I've poked around in the code a bit, and I see that the default for captures is 1024 (defaults.h:58), but it seems that it can be overridden, just not how I'm trying to do it. Any pointers? -- Jeff Abrahamson http://p27.eu/jeff/ http://transport-nantes.com/

haproxy architecture

xy notice based on requested hostname to which backend to dispatch requests. Is there any good wisdom here on how much to pile onto a single haproxy instance or when to stop? -- Jeff Abrahamson http://p27.eu/jeff/ http://transport-nantes.com/

Re: haproxy architecture

thers, 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, Alex Evonosky wrote: > You could make it a bit more agile and scale it: > > you can run them in &q

Re: haproxy architecture

ds to know about the virtual IP.  So > in DNS, you can create X amount of these pods  to distribute the load > among the pods. > > > and we run this setup in Apache mesos with about 100 dockers and 4 Ha > proxy pods. > > > > > On Mon, May 20, 2019 at 10:49 AM Je

Re: haproxy architecture

al: 1.1.1.4 > > > The mechanism to utilize the virtual IP is VRRP (apps like keepalived). > > > Then on the DNS server, you can use A records for 1.1.1.1 and 1.1.1.4 > > > On Mon, May 20, 2019 at 11:37 AM Jeff Abrahamson <mailto:j...@p27.eu>> wrote: > >