You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I'm experiencing an issue with the gRPC client library where it seems to be ignoring the endpoint path in the URL configuration. Here's a clear example of the problem:
Scenario:
I've configured the gRPC client using the AddCodeFirstGrpcClient method with the address set to "https://test-api.com/ms/er/"
csharp
Copy code
services.AddCodeFirstGrpcClient<ITestClient>((serviceProvider, o) =>
{
o.Address = new Uri("https://test-api.com/ms/er/");
}).ConfigureChannel(...).AddCallCredentials(...);
Within my interface definition, ITestClient, I have annotated the service contract with [ServiceContract(Name = "TestService")].
When I call a method on the client instance like this:
await testClient.GetUserExample(new RequestMessage() { Value = value });
Expected Behavior:
I expect the gRPC client to use the full URL I've provided (https://test-api.com/ms/er/) for the endpoint call. It should not omit the endpoint path (/ms/er/) from the URL.
Request:
I'd appreciate any insights or workarounds on how to properly configure the gRPC client to respect the full URL, including the endpoint path. If this is a limitation of the library, guidance on how to achieve the desired behavior or suggestions for alternative approaches would be very helpful.
The text was updated successfully, but these errors were encountered:
Description:
I'm experiencing an issue with the gRPC client library where it seems to be ignoring the endpoint path in the URL configuration. Here's a clear example of the problem:
Scenario:
I've configured the gRPC client using the AddCodeFirstGrpcClient method with the address set to "https://test-api.com/ms/er/"
csharp
Copy code
Within my interface definition, ITestClient, I have annotated the service contract with [ServiceContract(Name = "TestService")].
When I call a method on the client instance like this:
await testClient.GetUserExample(new RequestMessage() { Value = value });
The call is unexpectedly redirected to https://test-api.com/TestService/GetUserExample instead of respecting the full URL with the endpoint path (/ms/er/).
Expected Behavior:
I expect the gRPC client to use the full URL I've provided (https://test-api.com/ms/er/) for the endpoint call. It should not omit the endpoint path (/ms/er/) from the URL.
Request:
I'd appreciate any insights or workarounds on how to properly configure the gRPC client to respect the full URL, including the endpoint path. If this is a limitation of the library, guidance on how to achieve the desired behavior or suggestions for alternative approaches would be very helpful.
The text was updated successfully, but these errors were encountered: