On Thu, Feb 07, 2019 at 06:44:01PM +0200, Jarno Huuskonen wrote: > At least on my test case haproxy listens http2 and uses http/1.1 > to backend server > (example config and example backend server (in go) are in earlier > mail: https://www.mail-archive.com/[email protected]/msg32727.html > (just increase the header size (l in the go server) > 16309 and the > http2 connection between client <-> haproxy fails with frame error).
OK, I initially misunderstood the setup then. It would be possible that the client never advertised support for a larger frame and that we don't have a solution to deliver something that large. In fact the only option would be to fragment the output and build a CONTINUATION frame. I don't know how difficult it could be in this case :-/ > So the test setup is something like: > client(curl/chrome) -> http2/haproxy -> http/1.1/go server port 8081 > > I'll try with h2c and see if I can put it between client and haproxy. Then I suspect that you'll see haproxy either emit RST_STREAM or emit too large a frame and this frame get rejected. Thanks for the explanation! Willy
