Re: Quick update on pending HTTP/2 issues

Hi again guys, so another quick update on the subject : - the currently known POST issues have been resolved a few days ago, requiring a significant number of changes which make the code better anyway so it was not bad in the end ; - the abortonclose case has been solved as well. The

Re: Quick update on pending HTTP/2 issues

Hi Lukas! On Mon, Dec 11, 2017 at 11:54:07AM +0100, Lukas Tribus wrote: > Ok, the POST issue is obviously more important, but just to provide a > complete picture we also have those 2 minor issues left in H2, which > can easily be worked around though: Well, I could finally get rid of all the

Re: Quick update on pending HTTP/2 issues

Hi Lukas, On Mon, Dec 11, 2017 at 11:54:07AM +0100, Lukas Tribus wrote: > Hello Willy, > > > > 2017-12-07 19:55 GMT+01:00 Willy Tarreau : > > Guys, > > > > just to warn you, there's currently an issue affecting HTTP/2 with POST > > payloads to "slow" servers. > > Ok, the POST

Re: Quick update on pending HTTP/2 issues

Hello Willy, 2017-12-07 19:55 GMT+01:00 Willy Tarreau : > Guys, > > just to warn you, there's currently an issue affecting HTTP/2 with POST > payloads to "slow" servers. Ok, the POST issue is obviously more important, but just to provide a complete picture we also have those 2

Quick update on pending HTTP/2 issues

Guys, just to warn you, there's currently an issue affecting HTTP/2 with POST payloads to "slow" servers. It's a bit difficult to explain but in short if haproxy's buffers fill up during the transfer, there's a risk that the wakeup event to restart decoding once the buffer is released cannot be