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

Uninitialised Warn possible when using API Key policy on server level #5836

Closed
j1m-ryan opened this issue Jun 24, 2024 · 0 comments · Fixed by #5838
Closed

Uninitialised Warn possible when using API Key policy on server level #5836

j1m-ryan opened this issue Jun 24, 2024 · 0 comments · Fixed by #5838
Labels
bug An issue reporting a potential bug
Milestone

Comments

@j1m-ryan
Copy link
Member

Describe the bug
When using an API Key policy on the server level, it is possible to see an NGINX warning about an uninitialsed variable. This happens when visiting an undefined route.

To Reproduce

  1. Deploy the example in api key folder. (which has routes and /tea and /coffee but not /)
  2. curl cafe.example.com/
  3. See warn in console.
2024/06/24 15:21:43 [warn] 36#36: *4 using uninitialized "header_query_value" variable, client: 10.244.0.1, server: cafe.example.com, request: "GET / HTTP/1.1", subrequest: "/_validate_apikey_njs", host: "cafe.example.com"
10.244.0.1 - - [24/Jun/2024:15:21:43 +0000] "GET / HTTP/1.1" 401 179 "-" "curl/8.6.0" "-"

Expected behavior
Reaching an undefined route which is behind an API Key policy, should not have a warning in the logs.

Your environment

  • Version of the Ingress Controller - v3.6.0-snapshot
@vepatel vepatel added the bug An issue reporting a potential bug label Jun 25, 2024
@vepatel vepatel added this to the v3.6.0 milestone Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue reporting a potential bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants