Open nikoprotic opened 8 months ago
The answer here was to switch to TLS. wss://localhost:6457
and https://localhost:6457/...
both work as intended. Separately, The metrics endpoint returns good prometheus metrics, but the requests/events pages don't load anything.
Versions of relevant software used 0.15.0
What happened I have a simple ping-pong bidi stream RPC:
I auto-generate typescript client code and implement a client as described in the test files:
My server is a vanilla gRPC server written in C++, so I have spun up a docker-compose file with my server in one container, and the grpcwebproxy in another (I am exposing the relevant ports). I run the proxy with the following command:
(as you can see I've tried a few different things at this point).
With both my client and with postman, attempts to open websocket connections to
ws://localhost:6457
simply return "400 bad request". Furthermore, attempts to POST to the debug server withhttp://localhost:6458/debug/events
andhttp://localhost:6458/debug/requests
returns 'not allowed'. For what it's worth, GET to/metrics
works but returns a massive dump of data that is hard to decipher by hand.What you expected to happen
I expect websocket connections to open and stay open. I expect to receive data from the debug endpoints.
How to reproduce it (as minimally and precisely as possible):
See above.
Full logs to relevant components
Anything else we need to know