https://bz.apache.org/bugzilla/show_bug.cgi?id=59348
--- Comment #22 from Stefan Eissing <[email protected]> --- Slavko, have to look into this. From your description, I can see that clients behave differently. I assume that not all implementations agree how to follow the specifications. No surprise for a new protocol. I will check first with curl, since that also uses nghttp2. It at least waits until the end. Maybe the server sends something incorrect on closing the connection that curl does not like. We'll see. When that is working, I need to test Chrome. Have you already data on Firefox and Edge? Thanks. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
