https://bz.apache.org/bugzilla/show_bug.cgi?id=63835
--- Comment #14 from Konstantin Kolinko <knst.koli...@gmail.com> --- Tes(In reply to Konstantin Kolinko from comment #13) > (In reply to Mark Thomas from comment #11) > > My reading of the code and RFC 7230 is that it is acceptable to send this > > header to HTTP/1.0 clients when this code does this. [...] > > Ack. I agree. The recent commit in Git looks good. I tested master and 8.5.x, running WebSocket examples. No issues noted. Configuration option on <Connector> works correctly. Concatenation of values for Connection header works. (In reply to Konstantin Kolinko from comment #8) > > Smoke-testing HTTP/2.0, it works (at least in Firefox). > HTTP/2.0 works. (It was my error that I expected anything here. The "Upgrade" header is not used when testing with a browser and HTTPS, because negotiation happens with ALPN at connection time.) Keep-Alive header is not sent with HTTP/2.0, as expected. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
