-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Flatbuffers codec] Content-subtype only set for go lang #4213
Comments
Can you provide more details of how you ran the client/server, and the error you saw on each side? |
Sorry, it seems that it's an issue with the core lib, not setting the custom suffix |
The root cause might be core not setting custom suffix, but a panic in the go server should never happen. Do you have more information of where the panic happened? Can you paste the full stacktrace? Thanks. |
This should be the full trace I am getting out of the console. |
Thanks! |
Hello,
I am working on updating the flatbuffers Grpc support to v1.35.0 for all the languages that are implemented. However I am facing a small issue, whenever I try to make different languages communicate the go server would usually crash. Since I was told all the other languages actually ignore the appended suffix into the
application/grpc+{custom}
where custom is usually removed. I've dig into the code and found out that processHeaderField func has a comment about how it might be better if it was switched to (subtype).A suggested solution might be; checking for a
content-subtype
withinf hpack.HeaderField
and if present use that as a codec type/subtype, this can be set by the user as a custom metadata. and if its not it can default back to thecontent-type
It would be really nice to allow the go lang server to communicate with other Flatbuffers implemented clients.
Things I've tried:
The text was updated successfully, but these errors were encountered: