RE: Unable to modify haproxy stats url header

Hi Willy and Lukas, Could you please confirm, if we are planning to fix this in near feature. If yes, please let us know 1. In which build it will be available? 2. Are we backporting it to previous builds from which it got removed? Suraj Bora surb...@cisco.com Think before you print. This

Re: Unable to modify haproxy stats url header

On Mon, Oct 16, 2017 at 07:42:11AM +, Suraj Bora -X (surbora - HCL AMERICA INC at Cisco) wrote: > Hi Willy and Lukas, > > Could you please confirm, if we are planning to fix this in near feature. > If yes, please let us know Sure it will be worked on but it's very low priority considering

Re: Reload takes about 3 minutes

Just want to report that changing to another DNS server made it take about 2 seconds instead of 3 minutes :) Thanks for the help! Joel W Kall *Loop54* Barnhusgatan 20 111 23 Stockholm www.loop54.com Mobil: 073-5933 255 j...@loop54.com 2017-10-13 23:45 GMT+02:00

Re: Experimental / broken HTTP/2 support

Hi Pavlos! On Mon, Oct 16, 2017 at 10:46:44AM +0200, Pavlos Parissis wrote: > > Now after several failed attempts and with a lot of design sessions > > with my coworkers, I've made a good progress on a totally different > > approach which will later allow us to implement HTTP/2 on both sides, > >

Re: Experimental / broken HTTP/2 support

Hi Willy, On 2017-10-15 19:02, Willy Tarreau wrote: If everything goes well, the final rebased and cleaned up code should be available for a release candidate by the end of the month. Great, I will wait and see what you have available at the end of the month. I'm in no hurry, I just wanted

Re: Haproxy returns 502 before backend replies with 200

Hello again! So, I've used tcpdump to capture the traffic on both sides - Haproxy and on backend and ruled out the possible issue with Haproxy. It's clearly not the load balancer issue, it looks like some module on backend incorrectly sends a packet of binary service data (which most likely

Re: Experimental / broken HTTP/2 support

On 15/10/2017 07:02 μμ, Willy Tarreau wrote: > Hi Sander, > > On Sun, Oct 15, 2017 at 04:27:15PM +0200, Sander Klein wrote: >> Hi, >> >> I haven't been paying much attention to the list lately, but I am wondering >> what the current status of http/2 support is in 1.8-(dev|snapshot). >> >> Is it

Re: Experimental / broken HTTP/2 support

On 16/10/2017 11:27 πμ, Willy Tarreau wrote: > Hi Pavlos! > > On Mon, Oct 16, 2017 at 10:46:44AM +0200, Pavlos Parissis wrote: >>> Now after several failed attempts and with a lot of design sessions >>> with my coworkers, I've made a good progress on a totally different >>> approach which will

Re: Experimental / broken HTTP/2 support

Hi Willy, Willy Tarreau wrote on 16.10.2017: > Hi Pavlos! > On Mon, Oct 16, 2017 at 10:46:44AM +0200, Pavlos Parissis wrote: >> > Now after several failed attempts and with a lot of design sessions >> > with my coworkers, I've made a good progress on a totally different >> > approach which will

Re: Experimental / broken HTTP/2 support

On Mon, Oct 16, 2017 at 01:28:12PM +0200, Pavlos Parissis wrote: > I guess following step-by-step approach, 1st client side, it makes sense as > it reduces the size of breakage:-) Yes but not only this. It's also the fact that the main benefits of H2 are on the client side, where the latency is

Re: Experimental / broken HTTP/2 support

On 2017-10-16 14:19, Willy Tarreau wrote: On Mon, Oct 16, 2017 at 01:28:12PM +0200, Pavlos Parissis wrote: I guess following step-by-step approach, 1st client side, it makes sense as it reduces the size of breakage:-) Yes but not only this. It's also the fact that the main benefits of H2

Re: Experimental / broken HTTP/2 support

On Mon, Oct 16, 2017 at 08:07:17PM +0200, Sander Klein wrote: > On 2017-10-16 14:19, Willy Tarreau wrote: > > On Mon, Oct 16, 2017 at 01:28:12PM +0200, Pavlos Parissis wrote: > > > I guess following step-by-step approach, 1st client side, it makes > > > sense as > > > it reduces the size of

Re: Experimental / broken HTTP/2 support

Hi all, Aleksandar Lazic wrote on 16.10.2017: [snipp] > I have also started to create a image based on the h2 branch > https://gitlab.com/aleks001/haproxy18-centos > It's not finished yet but when it's finished you can use the docker > image then from docker hub. >

Balance Source until maxcon then force redispatch

Hi members of the list , I would like to know if you have any recommendation about this problem I have . I'm running haproxy with a backend of apache2 web servers to loadbalance HTTP services In this model, I have better performance with "balance source" so I visitor have the content

Re: Experimental / broken HTTP/2 support

Hi, On Sun, Oct 15, 2017 at 11:54:10PM +0500, ??? wrote: > 2017-10-15 23:43 GMT+05:00 Willy Tarreau : > > > On Sun, Oct 15, 2017 at 07:16:51PM +0100, Aaron West wrote: > > > Hi Willy, > > > > > > Sorry to bother you, just a quick question if I may. > > > > > > Does support

Re: Balance Source until maxcon then force redispatch

Hi Benoit, On Tue, Oct 17, 2017 at 04:17:42AM +0200, Benoit GEORGELIN - Association Web4all wrote: > Hi members of the list , > > I would like to know if you have any recommendation about this problem I have > . > I'm running haproxy with a backend of apache2 web servers to loadbalance HTTP >

Re: Random High Port load balancing for a single instance server

On Mon, Oct 16, 2017 at 01:00:53AM +, Tim Jones wrote: > Background Print Service Equitrac > > Load Balancing 2 back-ends high ports when service is restarted the service > comes up on a new random port, My backend config looks like this so I can > survive at least some windows updates, >

Re: Balance Source until maxcon then force redispatch

> Hi Benoit, > On Tue, Oct 17, 2017 at 04:17:42AM +0200, Benoit GEORGELIN - Association > Web4all > wrote: > > Hi members of the list , > > I would like to know if you have any recommendation about this problem I > > have > > . > > I'm running haproxy with a backend of apache2 web servers to