-
I'v found that enabled gRPC-Web Developer Tools (by SafetyCulture) brokes up unary interceptors set up for grpc-web client. Interceptors are being not called when gRPC-Web Developer Tools are enabled.…
-
We are using corporate proxy and all our outside traffic goes only through a proxy. I can't connect to internet without a proxy.
I'm trying to build new image based on another image.
Dockerfile …
-
### Is your feature request related to a problem? Please describe.
I'm implementing distributed tracing in a C++ application using gRPC and OpenTelemetry. My workflow involves creating spans with…
-
We recently started using Microcks for our gRPC APIs and really love the functionality and extensibility.
One feature we are currently missing for gRPC APIs are headers. Since headers (or in gRPC li…
-
### 🔍 Before submitting the issue
- [x] I have searched among the existing issues
- [ ] I am using a Python virtual environment
### 🐞 Description of the bug
Following is the workflow:
1. Settings …
-
## Expected Behavior
200 http status
## Actual Behavior
http 503 sometime
## Steps to Repr…
-
We currently use a simple HTTP/JSON protocol for the scaler to communicate with the interceptor. Because this protocol is just request/response, it has limitations on latency that can cause very slow …
-
As is, the current status interceptors that return an error if the wallet unlocker endpoints are hit while the wallet is already unlocked: https://github.com/lightningnetwork/lnd/blob/master/rpcperms/…
-
**Describe the solution you'd like**
We currently support server interceptors via [the `GRPC.Endpoint` module](https://hexdocs.pm/grpc/GRPC.Endpoint.html).
However, there seems to be no way to i…
-
Add an HTTP Interceptor implementation.
Currently we have a unary client/server grpc implementation, would be nice to have an HTTP implementation as well