Hi Willy, Just updated, and I can confirm, those fixes worked.
I had seen the commits in git, but didn't think they'd apply—thanks for pointing me back to them! I'm looking forward to all the other goodies we can deploy in 2.0.0! :-) Best, Luke — Luke Seelenbinder SermonAudio.com <http://sermonaudio.com/> | Senior Software Engineer > On Jun 19, 2019, at 09:50, Willy Tarreau <[email protected]> wrote: > > Hi Luke, > > On Wed, Jun 19, 2019 at 09:03:04AM +0200, Luke Seelenbinder wrote: >> Hi Willy, List, >> >> I seem to have great luck with HTX and finding obscure bugs. I upgraded to >> 2.0.0 on our main deployment recently (reasonably heavy load: 5k simultaneous >> conns, upwards of 1Gbps at times), and whenever HTX is enabled, I see very >> weird behavior: >> >> - First load typically works for primary domain, www. (html + assets, maybe >> 150 requests max; we're working on reducing this number ;) ) >> - First load never works for secondary domain, media. >> - All failed requests on secondary domain (same haproxy instance, different >> backend) timeout with a server data timeout (SD--) >> - A second (or third or fourth) reload of the primary page typically fails or >> hangs for a long time. If I wait ~2 minutes (roughly our timeout), it'll act >> like a first load. > > Christopher found that a bug used to affect H2 with the way cookies are > reassembled, from the early days of HTX. It's just that the recent updates > to HTX have emphasized the bug and made it actually affect traffic while > it didn't necessarily in the past. This explains the fact that it depends > on the request number. > > Please update to latest git, as Christopher has already backported the > fixes there. > > Thanks, > Willy
