Specified method is not supported

[m-ali-zafar]

I am trying to call grpc server that implements code first service. I am unable to call that service from client if I add CallOptions to the service method parameters for passing bearer token.

When I execute the client it throws the following exception:

Unhandled exception. System.NotSupportedException: Specified method is not supported. at ProtoBuf.Grpc.Internal.Proxies.ClientBase.ICustomerService_Proxy_0.ICustomerService.CreateCustomer(CreateCustomerCommand , CallOptions )

If I remove the CallOptions parameter and then execute the call it works perfectly as it should.

Additionally, package referenced in client and server have the same version.

Service Implementation

    [Authorize]
    public class CustomerService : ICustomerService
    {
        IMediator _mediator;
        public CustomerService(IMediator mediator)
        {
            _mediator = mediator;
        }

        public Task CreateCustomer(CreateCustomerCommand request, CallOptions callOptions)
        {
            return _mediator.Send(request);
        }
    }

[mgravell]

short version: use CallContext, not CallOptions; CallContext has a .CallOptions, or many of the expected features are directly available (for example, .RequestHeaders, .CancellationToken, etc)

longer version: protobuf-net.Grpc, being code-first, attempts to unify the client and server APIs so that the same interface (presumably ICustomerService in this case) makes sense for both the client and server side. This is not possible with CallOptions (client) vs ServerCallContext (server), so protobuf-net.Grpc creates CallContext which bridges the gap between both

[m-ali-zafar]

thanks @mgravell that worked.

One more thing I would like to ask. Why is it that a grpc service running on kestrel works perfectly fine but a service running on IIS throws unexpected errors?

[mgravell]

If you don't tell me exactly what unexpected errors it is throwing, I can't really comment - but my first guess would be "is http/2 configured? can IIS even use http/2?"

[m-ali-zafar]

I am using iis 10.0 that supports http/2. When I start a grpc service on local machine and connect a local client to it. Client request is sent to the server and returns a valid response. However client throws the following exception

Grpc.Core.RpcException: Status(StatusCode="Cancelled", Detail="Error starting gRPC call. IOException: The request was aborted. Http2StreamException: The HTTP/2 server reset the stream. HTTP/2 error code 'CANCEL' (0x8).", DebugException="System.IO.IOException: The request was aborted.

[mgravell]

Ultimately, protobuf-net.Grpc doesn't handle these details itself - it simply sits on top of the transport provided either by Google (Grpc.Core) or Microsoft (Grpc.AspNetCore, for the server); I don't know all the details of what happens internally. I would first say:

"if you create a very basic hello-world service using the vanilla .proto-first experience: does that work?"

If that doesn't work: protobuf-net.Grpc doesn't stand a chance, as the problem is at a layer below, that we don't maintain or support. If it does work: I can happily step in to try to investigate the difference.

If the vanilla test doesn't work; I'd suggest that asking over on the main grpc-dotnet repo would be the next step.

[menaheme]

Http2 requires https , is iis binding configuration in place for that?

…

On Wed, Aug 17, 2022, 7:08 PM Marc Gravell ***@***.***> wrote: Ultimately, protobuf-net.Grpc doesn't handle these details itself - it simply sits on top of the transport provided either by Google (Grpc.Core) or Microsoft (Grpc.AspNetCore, for the server); I don't know all the details of what happens internally. I would first say: "if you create a very basic hello-world service using the vanilla .proto-first experience: does *that* work?" If that doesn't work: protobuf-net.Grpc doesn't stand a chance, as the problem is at a layer below, that we don't maintain or support. If it *does* work: I can happily step in to try to investigate the difference. — Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLOIH2WCGZBR3T7TQYOR33VZUFANANCNFSM56YGTV7A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mgravell]

@menaheme nit: that's not exactly true; http/2 definitely recommends TLS, but it can work without. Kestrel has problems trying to support H1 and H2 on the same port without TLS (a H2-only non-TLS endpoint is fine), and if you're saying "H2 inside IIS specifically: requires TLS", then: I would readily believe you.

[menaheme]

Yes thats what i meant, iis will not by deafault allow http2 without tls

…

On Wed, Aug 17, 2022, 8:58 PM Marc Gravell ***@***.***> wrote: @menaheme <https://github.com/menaheme> nit: that's not exactly true; http/2 definitely *recommends* TLS, but it can work without. Kestrel has problems trying to support H1 and H2 on the same port without TLS, and if you're saying "H2 inside IIS specifically: requires TLS", then: I would readily believe you. — Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLOIHYIO4WIVWZM2MOZDETVZUR3DANCNFSM56YGTV7A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[m-ali-zafar]

I actually had a https binding for that service added. I tried to make a client request to simple contract first application but that too
failed.

Grpc.Core.RpcException: Status(StatusCode="Cancelled", Detail="No grpc-status found on response.")