kong
kong copied to clipboard
In Kong 3.6, X-Kong-Request-Debug-Output is not provided in the response header for successful scenarios
Is there an existing issue for this?
- [X] I have searched the existing issues
Kong version ($ kong version
)
Kong 3.6
Current Behavior
When including the X-Kong-Request-Debug-Token and X-Kong-Request-Debug headers in the request, according to Kong's documentation (https://docs.konghq.com/gateway/latest/production/debug-request/), the X-Kong-Request-Debug-Output doesn't show up in the response header for successful requests with an HTTP response code of 200.
In previous versions (version 3.5), the X-Kong-Request-Debug-Output would appear in the response header for all HTTP response codes (2XX, 4XX, and 5XX).
Expected Behavior
When including the X-Kong-Request-Debug-Token and X-Kong-Request-Debug headers in the request, according to Kong's documentation (https://docs.konghq.com/gateway/latest/production/debug-request/), the X-Kong-Request-Debug-Output should show up in the response header even for successful requests with an HTTP response code of 200.
Steps To Reproduce
No response
Anything else?
No response
@SSukhada Thanks for your report, I can't reproduce your issue on my machine, could you give us more detailed steps to reproduce it?
Internal ticket: KAG-4296
This issue is marked as stale because it has been open for 14 days with no activity.
Dear contributor,
We are automatically closing this issue because it has not seen any activity for three weeks. We're sorry that your issue could not be resolved. If any new information comes up that could help resolving it, please feel free to reopen it.
Your contribution is greatly appreciated!
Please have a look our pledge to the community for more information.
Sincerely, Your Kong Gateway team