We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$ kong version
Kong 3.8.1
I followed the guide to use the grpc-gateway plugin as described in the https://docs.konghq.com/hub/kong-inc/grpc-gateway/how-to/ However, the provided example for making gRPC calls using curl does not work as described.
The guide suggests using the following command:
curl -XGET localhost:8000/v1/messages/Kong2.0
But this command fails unless I explicitly add the --header "te: trailers" option, like this:
curl -XGET --header "te: trailers" localhost:8000/v1/messages/Kong2.0
Can the Kong developers make the grpc-gateway plugin automatically add the te: trailers header to gRPC requests?
No response
The text was updated successfully, but these errors were encountered:
Duplicate issue #14043 ?
refer to fix: https://github.com/Kong/kong/pull/14042/files
Sorry, something went wrong.
No branches or pull requests
Is there an existing issue for this?
Kong version (
$ kong version
)Kong 3.8.1
Current Behavior
I followed the guide to use the grpc-gateway plugin as described in the https://docs.konghq.com/hub/kong-inc/grpc-gateway/how-to/
However, the provided example for making gRPC calls using curl does not work as described.
The guide suggests using the following command:
curl -XGET localhost:8000/v1/messages/Kong2.0
But this command fails unless I explicitly add the --header "te: trailers" option, like this:
curl -XGET --header "te: trailers" localhost:8000/v1/messages/Kong2.0
Can the Kong developers make the grpc-gateway plugin automatically add the te: trailers header to gRPC requests?
Expected Behavior
No response
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: