For #2, Go does not expose or respect any max header size settings. We do have an issue to start respecting the http2 setting:
https://github.com/grpc/grpc-go/issues/1291 On Tuesday, March 13, 2018 at 3:16:03 AM UTC-7, [email protected] wrote: > > Hi, > > Had 2 questions regarding using "grpc.max_metadata_size" > > 1. It was not clear to me that `max_metadata_size` takes into account size > of "detail" part of response. Can we allow setting "max_metadata_size" to > -1 to represent unlimited as with `max_send_message_length` and > `max_receive_message_length`? > > The exception that gets raised (at least from python) when you try and > return with details larger then `max_metadata_size` is > `(StatusCode.RESOURCE_EXHAUSTED, to-be-sent trailing metadata size exceeds > peer limit` which imo is somewhat confusing as I didn't consider "details" > to be trailing metadata, and it does not show up under the response call > trailing metadata. > > 2. Is the equivalent of "max_metadata_size" exposed anywhere in grpc-go? > As far as I can tell Java does expose it through netty params > `maxHeaderListSize`. > > Thanks, > Ashwin > > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/49e5bcc6-db00-41db-9a44-2554afe9a3ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
