Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle HTTP/2 upgrade response from the stream 1 #66

Merged
merged 1 commit into from
Dec 9, 2015

Conversation

trustin
Copy link
Member

@trustin trustin commented Dec 9, 2015

Motivation:

Once an upgrade to HTTP/2 is finished in a cleartext connection, the
server sends the response for the upgrade request to the client via the
stream 1. Armeria client currently does not handle it explicitly,
causing the response to reach at the end of the pipeline. This is not
necessarily harmful, but it will pollute our DEBUG log level because
Netty will log any messages that reach at the end of the pipeline.

Modifications:

  • Make UpgradeHandler handle the upgrade response so that Netty does not
    complain
  • Change the next version to 0.6.1.Final

Result:

Less noisy log messages

@trustin trustin added the defect label Dec 9, 2015
@trustin trustin added this to the 0.6.1.Final milestone Dec 9, 2015
@@ -60,8 +61,10 @@
import io.netty.handler.codec.http2.Http2ConnectionHandler;
import io.netty.handler.codec.http2.Http2FrameReader;
import io.netty.handler.codec.http2.Http2FrameWriter;
import io.netty.handler.codec.http2.Http2Headers.PseudoHeaderName;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unused import.

Motivation:

Once an upgrade to HTTP/2 is finished in a cleartext connection, the
server sends the response for the upgrade request to the client via the
stream 1. Armeria client currently does not handle it explicitly,
causing the response to reach at the end of the pipeline. This is not
necessarily harmful, but it will pollute our DEBUG log level because
Netty will log any messages that reach at the end of the pipeline.

Modifications:

- Make UpgradeHandler handle the upgrade response so that Netty does not
  complain
- Change the next version to 0.6.1.Final

Result:

Less noisy log messages
@blmarket
Copy link
Contributor

blmarket commented Dec 9, 2015

LGTM. 👍

blmarket added a commit that referenced this pull request Dec 9, 2015
Handle HTTP/2 upgrade response from the stream 1
@blmarket blmarket merged commit ebcd63c into line:master Dec 9, 2015
@trustin trustin deleted the handle_upgrade_response branch December 17, 2015 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants