The behavior you're describing is odd. The ResponseHeaderAsync metadata is something the client should be able to receive as soon as the server writes them (without needing to wait for the entire call to finish or receiving any responses from the server). The way to force sending the response headers on the server is by invoking serverCallContext.WriteResponseHeadersAsync() (if you don't force sending the response headers explicitly, they will be sent along with the first response sent by server).
On Wednesday, February 17, 2021 at 6:46:13 PM UTC+1 [email protected] wrote: > When making a streaming RPC call, the client returns immediately, before > the server-side interceptor is executed. The interceptor is doing a > security check and would throw an RpcException prior to calling the > continuation. What event occurs that could be hooked or detected to allow > the client to know it has passed the initial security check? The > ResponseHeadersAsync task does not appear to complete until the stream is > closed. Thank you. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/7273cf5b-f11d-46ad-a425-4f6035dda7a6n%40googlegroups.com.
