Closed lassemand closed 1 year ago
The issue is that curl will make a http1.1 request by default, and unless you enable grpc-web the server that is started will not support http1.1 since grpc goes over http2. You can force curl to use http2 by using --http2-prior-knowledge
and then you'll get a status code 12 (UNIMPLEMENTED)
It would be weird to enable http1.1 just to support a nice error message in this context.
Description
When not having grpcweb enabled, and requesting a resource under the path of a grpcweb resource, I expect a proper response like for example 404
Steps to Reproduce
Not having set CONCORDIUM_NODE_GRPC2_ENABLE_GRPC_WEB set to true and requesting
Expected Result
At the very least a proper status code. Ideally even a nice little message indicating that grpcweb endpoints are not enabled
Actual Result
Versions