On Wednesday, February 1, 2017 at 8:52:57 AM UTC-8, Mark D. Roth wrote: > > What character encoding do they use for that field, UTF-8? How can we >>> tell what character encoding is in use? I think we'd need some way to >>> figure this out in order to support it. >>> >> >> it is raw bytes, so no encoding (it is a serialized internal protobuf) >> It does not require splitting (in fact any modification would be harmful) >> Maybe make the delimiter optional? (and when it is set, the field must be >> a string). >> > > Actually, I think there's a more fundamental problem here. HTTP2 headers > are limited to ASCII characters (see > https://tools.ietf.org/html/rfc7540#section-10.3). Given that, the only > way we could support this would be to encode it somehow in the header value. >
Isn't this a problem for strings as well, as currently defined in the gRFC? How are strings containing non-ASCII or illegal characters handled? > -- 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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. 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/1403c8d6-4535-46ee-9174-c0c0ed4addc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
