-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Include SETTINGS_MAX_HEADER_LIST_SIZE in initial SETTINGS. #2350
Comments
Opened Netty PR netty/netty#5919 |
Does anything need to be done here? Will the next update of Netty "just work"? |
@ejona86 We need to also include the max header list value in the initial settings. So add one line in client handler and one line in server handler. [1]
|
lukaszx0
added a commit
to lukaszx0/grpc-java
that referenced
this issue
Feb 10, 2017
lukaszx0
added a commit
to lukaszx0/grpc-java
that referenced
this issue
Feb 12, 2017
carl-mastrangelo
pushed a commit
that referenced
this issue
Feb 13, 2017
For posterity and people that are using versions This fixes following stream error which gets thrown when header size is exceeded:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We currently don't send
SETTINGS_MAX_HEADER_LIST_SIZE
as part of the initialSETTINGS
frame, although we enforce it on the decoder. This is valid as of the H2 specHowever, we would argue that we should still include it in the initial
SETTINGS
frame, cause why not? If both endpoints are gRPC Java, it would also give us better error messages, as then the local encoder would enforce the remote decode limit [1]. However, we can't currently do that cause it seems like a bug in Netty that the encoder throws a connection error and not a stream error [1], bringing down the whole connection, while only the stream should fail. I ll open a issue/PR in Netty.[1] https://github.com/netty/netty/blob/4.1/codec-http2/src/main/java/io/netty/handler/codec/http2/internal/hpack/Encoder.java#L126
The text was updated successfully, but these errors were encountered: