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 issues affecting the POST, and some of them required quite complex setups just to get the proper time race to trigger them! So I could get back to these two parts : > - the abortonclose incompatibility: > https://www.mail-archive.com/[email protected]/msg28186.html I'm currently estimating what it would cost to mirror the flag into the stream instead of checking it in the proxy, and to always clear it from H2 streams. > - improper close (no GOAWAY) when "timeout server" < "timeout client" > https://www.mail-archive.com/[email protected]/msg27990.html I totally failed to reproduce this one for now. I properly get the 504 timeout as a HEADERS frame, then later I'm seeing the GOAWAY(0) frame indicating a connection close on idle. I also tried with the master prior to the POST fixes and it did the same, though maybe something changed since you last saw this. I'm interested in getting a double-check on this in the development branch. Thanks! Willy
