failed to set X-Kong-Upstream-Status header while sending to client #12994
Labels
pending author feedback
Waiting for the issue author to get back to a maintainer with findings, more details, etc...
stale
Comments
|
Could you upgrade kong to latest 3.6.x and try again? We always suggest our user to use the latest version. |
chronolaw
added
the
pending author feedback
|
This issue is marked as stale because it has been open for 14 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Kong version (
$ kong version)2.8.0
Current Behavior
from kong log, below error can be seen:
2024/04/18 16:35:00 [error] 28#0: *28981717 [lua] handler.lua:1524: before(): failed to set X-Kong-Upstream-Status header while sending to client, client: xxx, server: kong, request: "GET /profiles/list HTTP/1.1", host: "xxx"
and all requests will fail with status 403
Expected Behavior
should have no such error
Steps To Reproduce
deploy kong 2.8.0 and ingress controller 2.3.1
register some upstream services, and routes
keep calling those registered routes in a long running job
Anything else?
No response
The text was updated successfully, but these errors were encountered: