March 19, 2019 - Why two music-streaming giants have entered India in less than a month

2019-03-19 Thread TradeBriefs

Re: High p99 latency with HAProxy 1.9 in http mode compared to 1.8

2019-03-19 Thread Ashwin Neerabail
Hi Willy, I have saved the stats page of both server haproxy ( egress) and client haproxy (ingress) : https://cloud.box.com/s/5wnnm0mcrla1w28101g6jtjkod5p0ryt - did you enable threads on 1.9 ? On the test setup, for the client haproxy, its set to 1 thread ( 1 core). On production yes. On the

Re: 400 SC on h2 xhr post

2019-03-19 Thread Jarno Huuskonen
Hi, On Tue, Mar 19, Maximilian Böhm wrote: > The problem I experience is within a legacy javascript application which > periodically checks if the user is still logged in. It does so by sending an > xhr request every 30 seconds (I said, it's a legacy app, right? It does so by > POST not

question about -p and -sf/-st

2019-03-19 Thread Marc Fournier
Hello, I have a script which is reloading haproxy by running: haproxy -p /var/run/haproxy.pid -sf $(cat /var/run/haproxy.pid) [...] and noticed that occasionnally the pidfile was empty, leading to the old process not getting killed. I'm struggling to understand *why* the pidfile is

Re: Status Codes in H2 Mode

2019-03-19 Thread Luke Seelenbinder
Hi Willy, > Yes definitely. There's no emergency but any extra info you can provide > will help us of course. I tested with HTTP/1.1 on the client side and HAProxy was flawless, so this is very, very likely limited to h2. > That could indeed. No need to have something very advanced, if you

AW: 400 SC on h2 xhr post

2019-03-19 Thread Maximilian Böhm
Hello Willy, thanks for your suggestions. >> There are two things you can try : >> 1) please issue "show errors" on your CLI when this happens >> 2) you can enable the HTX mode I did both. Though It was not really a success... What could I do next? Everything - browser, docker/haproxy and the

Re: 400 SC on h2 xhr post

2019-03-19 Thread Willy Tarreau
Hi Maximilian, On Tue, Mar 19, 2019 at 01:17:52PM +, Maximilian Böhm wrote: > 172.17.0.1:46372 [19/Mar/2019:12:10:43.465] [fntnd] [bknd] 0/0/0/-1/8 400 187 > - - CH-- 1/1/0/0/0 0/0 "POST [URL] HTTP/1.1" This one could indicate a client close while uploading the contents, but it could also

[ANNOUNCE] haproxy-1.9.5

2019-03-19 Thread Willy Tarreau
Hi, HAProxy 1.9.5 was released on 2019/03/19. It added 81 new commits after version 1.9.4. I'm sorry it took longer than initially expected but the complexity of certain bugs creates some reluctance to issue an intermediary release when you don't fully trust the pending fixes yet. Only well

Re: Status Codes in H2 Mode

2019-03-19 Thread Willy Tarreau
On Tue, Mar 19, 2019 at 08:59:38AM -0400, Luke Seelenbinder wrote: > Makes sense, Willy. Thanks for continuing to investigate this. > > > I'm assuming that this is always reproducible with H2 on the front and > > H1 on the back. > > I have not tried it with H1 -> H1, but I assume that case works

400 SC on h2 xhr post

2019-03-19 Thread Maximilian Böhm
N¬ŠÆ§Kó0K"‚w™ë,j‚¹ÓQp·Ó]Ä÷ÞÂQ@Ó¯S¢©®Œr~ŠæŠ[±¢¸!jšèÇ'è®h¥»++›ç-ãM ‰áÛk¦‹- «^NçµôÆ«ÛM}×}{ço´ÓM¢{^žÒڞ šç^ @¨ž×§µ<©z×±·úej)܅ªìz

Re: Status Codes in H2 Mode

2019-03-19 Thread Luke Seelenbinder
Makes sense, Willy. Thanks for continuing to investigate this. > I'm assuming that this is always reproducible with H2 on the front and > H1 on the back. I have not tried it with H1 -> H1, but I assume that case works correctly. Would it be helpful if I proved it one way or the other? > I'll