James Newton-King
James Newton-King
Kestrel caches some reusable buffers that are used for HTTP requests. Those are held onto forever and aren't released. It's something that's been considered but hasn't been reported as a...
There are many problems making a server call a client like firewalls and NAT addressing. A better solution is for clients to connect to the server and establish an ongoing...
> Is there no other way than using the streaming? Streaming is the only way I know how. 1. The client establishes a server streaming call 2. The client listens...
This sounds like a NuGet or assembly loading problem. The lowest valid version for all apps should be chosen, which is 6.0.0 here. There isn't anything to fix in gRPC...
> However, in the instance the url is correct, but the server port is secure and the used url is not secure (or vice versa), channel.ConnectAsync() works, and the channel...
I'd like to support it, but it requires changes in the .NET networking layer.
No plans at the moment. It might be possible to replicate the logic here - https://github.com/SafetyCulture/grpc-web-devtools/blob/c5a71e2168c40eb55aa094402e519580e109528d/public/content-script.js - and send events to the window using a .NET interceptor. That would allow...
No plans at the moment. There hasn't been much developer interest so it isn't a high priority.
The proxy is customized on SocketsHttpHandler which is set on GrpcChannelOptions.HttpHandler. I don't think SocketsHttpHandler has the equivalent of `grpc.max_metadata_size`. Are large headers/trailers a problem with Grpc.Net.Client?
What is the exception? Can you add the message + stack trace to this issue? gRPC removes some of the exception detail. To get the original error you might need...