Hi Robin, On Fri, Jan 11, 2013 at 11:10:06AM -0800, Robin Lee Powell wrote: > [reordered] > > On Fri, Jan 11, 2013 at 07:14:05PM +0100, Lukas Tribus wrote: > > > > If you are running -dev, its probably a good idea to follow the > > mailing list closely and eventually read the commit message on > > git. > > It's hard because I only give one day a week to this company, but > I'll see what I can do; thanks for the warning.
Yes indeed, people running -dev should subscribe to the list. You'll get some spam, so use a dedicated folder for this and you'll be fine. If you don't have time, only read the announces, the mails that seem to discuss concerns related to yours, and the very long threads which generally indicate a hard to reproduce bug. Most other posts are assistance and suggestions you probably don't care about for one day a week ! If following the list is too hard at this rhythm, maybe you'd better avoid -dev instead. > > Its this line in the changelog: BUG/MEDIUM: stream interface: fix > > possible stalls during transfers > > > > The changelog comes from the commit line, but that line explains > > the fix itself, not the possible symptoms of the bug it addresses. > > To understand all the details of a change, I suggest your read the > > commit message [1]. > > > > [1] > > http://haproxy.1wt.eu/git?p=haproxy.git;a=commit;h=ca00fbcb91165e5d8d64ba7b53000ffac77f44c9 > > That sounds like an intermittent sort of thing; it also doesn't > sound tied to the acl choices. What I'm seeing is that this happens > *every* time with *every* user if the sni acl is used, and never > with any user if it isn't. Having said that, I know nothing > whatsoever about haproxy internals, so I'll try dev17 and let you > know. :) Indeed, there were multiple bugs with the POST issue, each one hiding another. For Sander (the reporter), the problem was very reproducible, while I could never get it. I suspect you're hitting the same one. Note that the fix above was finally not the last one, but all were merged in dev17. A few minor bugs were fixed since, all of them are fine in haproxy-ss-20130108.tar.gz. So you may use this one instead to get rid of any possible known issue. Regards, Willy
