Skip to content
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

In Kong 3.6, X-Kong-Request-Debug-Output is not provided in the response header for successful scenarios #12866

Closed
1 task done
SSukhada opened this issue Apr 16, 2024 · 3 comments
Labels
pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... stale

Comments

@SSukhada
Copy link

Is there an existing issue for this?

  • 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

@ADD-SP
Copy link
Contributor

ADD-SP commented Apr 24, 2024

@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

@ADD-SP ADD-SP added the pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... label Apr 24, 2024
Copy link
Contributor

github-actions bot commented May 9, 2024

This issue is marked as stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label May 9, 2024
Copy link
Contributor

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending author feedback Waiting for the issue author to get back to a maintainer with findings, more details, etc... stale
Projects
None yet
Development

No branches or pull requests

2 participants