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
The io.netty.example.http2.helloworld.client.Http2Client example should work in the h2c (HTTP2 cleartext - non-TLS) mode, which is the default for this example unless you set a -Dssl VM param.
Actual behavior
The initial h2c upgrade (HTTP 1 request with upgrade: h2c header) does not contain a host header due to this missing in the Http2ClientUpgradeCodec.setUpgradeHeaders() method, leading to the below console output:
Connected to [127.0.0.1:8080]
User Event Triggered: UPGRADE_ISSUED
User Event Triggered: UPGRADE_REJECTED
Exception in thread "main" java.lang.IllegalStateException: Timed out waiting for settings
at io.netty.example.http2.helloworld.client.Http2SettingsHandler.awaitSettings(Http2SettingsHandler.java:49)
at io.netty.example.http2.helloworld.client.Http2Client.main(Http2Client.java:107)
and the following in wireshark (i.e. the h2c server rejects the upgrade request):
Minimal yet complete reproducer code (or URL to code)
n/a - issue with existing io.netty.example.http2.helloworld.client.Http2Client example
Netty version
4.1 branch (seen issue in latest and 4.1.315)
JVM version (e.g. java -version)
1.8.0_201
OS version (e.g. uname -a)
Ubuntu 18.04.2
The text was updated successfully, but these errors were encountered:
TristanPerry
changed the title
http2.helloworld.client example fails for h2c (no-TLS) mode
Http2ClientUpgradeCodec makes invalid HTTP1 request (hence http2.helloworld.client example fails for h2c mode)
May 14, 2019
… upgrade request
Motivation:
The io.netty.example.http2.helloworld.client.Http2Client example should work in the h2c (HTTP2 cleartext - non-TLS) mode, which is the default for this example unless you set a -Dssl VM param. As we do not set the HOST header some servers do reject the upgrade request.
Modifications:
Set the HOST header
Result:
Fixes#9115.
… upgrade request (#9177)
Motivation:
The io.netty.example.http2.helloworld.client.Http2Client example should work in the h2c (HTTP2 cleartext - non-TLS) mode, which is the default for this example unless you set a -Dssl VM param. As we do not set the HOST header some servers do reject the upgrade request.
Modifications:
Set the HOST header
Result:
Fixes#9115.
… upgrade request (#9177)
Motivation:
The io.netty.example.http2.helloworld.client.Http2Client example should work in the h2c (HTTP2 cleartext - non-TLS) mode, which is the default for this example unless you set a -Dssl VM param. As we do not set the HOST header some servers do reject the upgrade request.
Modifications:
Set the HOST header
Result:
Fixes#9115.
Expected behavior
The
io.netty.example.http2.helloworld.client.Http2Client
example should work in the h2c (HTTP2 cleartext - non-TLS) mode, which is the default for this example unless you set a-Dssl
VM param.Actual behavior
The initial h2c upgrade (HTTP 1 request with
upgrade: h2c
header) does not contain ahost
header due to this missing in theHttp2ClientUpgradeCodec.setUpgradeHeaders()
method, leading to the below console output:and the following in wireshark (i.e. the h2c server rejects the upgrade request):
Steps to reproduce
Http2Client
example.Minimal yet complete reproducer code (or URL to code)
n/a - issue with existing
io.netty.example.http2.helloworld.client.Http2Client
exampleNetty version
4.1 branch (seen issue in latest and 4.1.315)
JVM version (e.g.
java -version
)1.8.0_201
OS version (e.g.
uname -a
)Ubuntu 18.04.2
The text was updated successfully, but these errors were encountered: