-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
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
gRPC-JSON Transcoder did not response with 504 when route timeout reached #2275
Labels
question
Questions that are neither investigations, bugs, nor enhancements
Comments
mattklein123
added
the
question
Questions that are neither investigations, bugs, nor enhancements
label
Dec 29, 2017
@lizan you mind taking a look at this when you have a few moments? |
Thanks for reporting @arifsetiawan, I believe it is a bug in transcoder filter and I will fix it soon. |
htuch
pushed a commit
that referenced
this issue
Jan 17, 2018
Make gRPC-JSON transcoder not buffering response at end_stream or non-gRPC response. Risk Level: Low Testing: unit test Docs Changes: N/A Release Notes: N/A Fixes #2275 Signed-off-by: Lizan Zhou <zlizan@google.com>
Shikugawa
pushed a commit
to Shikugawa/envoy
that referenced
this issue
Mar 28, 2020
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
jpsim
pushed a commit
that referenced
this issue
Nov 28, 2022
Description: The ':authority' header is used to direct the connection internally and this is set when initializing the builder. Fixes #2244. Risk Level: Low Testing: Unit Signed-off-by: Mike Schore <mike.schore@gmail.com> Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
pushed a commit
that referenced
this issue
Nov 29, 2022
Description: The ':authority' header is used to direct the connection internally and this is set when initializing the builder. Fixes #2244. Risk Level: Low Testing: Unit Signed-off-by: Mike Schore <mike.schore@gmail.com> Signed-off-by: JP Simard <jp@jpsim.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Template
Title: gRPC-JSON Transcoder did not response with 504 when route timeout reached
Description:
.proto
Golang server
Envoy version
Envoy config
If I tried with Node.js grpc client
I will get following error message after several seconds
I think is coming from Envoy because of route timeout setting.
If I use curl to access HTTP API, I expect HTTP API should also response with HTTP status 504. I found that I don't get error reply from server and connection keep open
The text was updated successfully, but these errors were encountered: