On Tue, Jan 22, 2019 at 09:42:53AM +0000, Luke Seelenbinder wrote: > Hi Willy, Aleks, > > I will try the things suggested this afternoon (hopefully) or tomorrow and > get back to you. > > > At least if nginx does this it should send a GOAWAY > > frame indicating that it will stop after stream #2001. > > That's my understanding as well (and the docs say as much).
OK. > I assumed HAProxy > would properly handle it, as well, so perhaps it's something else nefarious > going on in our particular setup. Or we might have a bug there as well. I'll recheck the code just in case I spot anything. > There is still the possibility that the bug > fixed by Aleks' patches regarding HTX & headers were causing this issue in a > back-handed sort of way. I will apply those patches, establish that the > headers bug is fixed, and then try the recommendations from this bug to rule > out any interactions on that side (a badly written header in our situation > could result in a 404, which seemed to be the worst user-facing case of this > bug). Sure, let's address one problem at a time :-) Willy
