You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the above and make an HTTP/1.1 request to localhost:8080 such as curl localhost:8080. It also fails when attempting an upgrade to HTTP/2 such as curl --http2 localhost:8080. It works when assuming prior knowledge and using HTTP/2 from the outset such as curl --http2-prior-knowledge localhost:8080.
… HTTP server supports both HTTP/1.1 and HTTP/2 clear text
Remove the extra HTTP/1.1 handlers from the pipeline when upgrading from HTTP/1.1 to HTTP/2 clear text
Fixes#1610
… HTTP server supports both HTTP/1.1 and HTTP/2 clear text (#1611)
Remove the extra HTTP/1.1 handlers from the pipeline when upgrading from HTTP/1.1 to HTTP/2 clear text
Fixes#1610
wilkinsona
changed the title
Any HTTP/1.1 request causes an NPE when using HTTP11 and H2C protocols and accessing logging is enabled
Any HTTP/1.1 request causes an NPE when using HTTP11 and H2C protocols and access logging is enabled
Apr 26, 2021
Expected Behavior
Access logging should work.
Actual Behavior
Enabling access logging causes a
NullPointerException
inAccessLogHandlerH1.write
.Steps to Reproduce
Run the above and make an HTTP/1.1 request to localhost:8080 such as
curl localhost:8080
. It also fails when attempting an upgrade to HTTP/2 such ascurl --http2 localhost:8080
. It works when assuming prior knowledge and using HTTP/2 from the outset such ascurl --http2-prior-knowledge localhost:8080
.Your Environment
netty
, ...): Netty 4.1.63java -version
): openjdk version "1.8.0_282"uname -a
): macOS 10.15.7The text was updated successfully, but these errors were encountered: