-
Notifications
You must be signed in to change notification settings - Fork 772
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
Problem with getting response metadata from the Unary Interceptors API #909
Comments
There are 2 concepts here: initial metadata vs trailing metadata. In your callback-based example above, you are accessing the trailing metadata via the In your promise-based interceptor, Similarly, in your callback-based client, See this unit test on how to access both the initial and trailing metadata in your promise-based |
@stanley-cheung, I use the JavaScript implementation compare with the After that, I try to develop the |
Ah. I see. You probably run into this particular issue: #877 (comment), where some of the symbols/functions for the |
* Fix CI exit code reporting * Simplify local integration test usage * Fixed webpack compatibility with old browsers (safari 9) * Upgrade karma * Disabled websocket tests for old versions of firefox * Removed firefox 21 due to SSL incompatibility * Updated latest browser versions * Revert "added websocket transport to cancel propagation test (grpc#904)"
I try to implement the Promise-based client with my gRPC-web and I have a problem with getting metadata from
Unary Interceptors
API. In the gRPC blog: https://grpc.io/blog/grpc-web-interceptor/ they recommend using theresponse.getMetadata()
in the Unary Interceptors invoker callback. So after the implementation, my response metadata is returned only ax-envoy-upstream-service-time
However, if I use the gRPC-web callback-based API. It must return my custom value in status metadata. Thank you for the advice!
The text was updated successfully, but these errors were encountered: