-
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
fix(runloop): query args not forwarded bug #11328
fix(runloop): query args not forwarded bug #11328
Conversation
|
7043f70
to
37d21ed
Compare
@samugi Can this change be released in the next patch version of Kong 3.3.x? |
In general, we do not do this backport to the old kong community old version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly is Okay for me, Please fix failure CI!
5085407
to
573361a
Compare
The DB less integration test is still failing, and I am unsure as to why. Should this test be skipped for db less? |
I noticed that the tests I was running on local were only running for Update: |
573361a
to
0259c92
Compare
@oowl @samugi
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @chirag-manwani for your efforts writing this test.
Would you mind moving it out of the 02-router_spec.lua
file, since this is not exactly a router test? I believe it would be appropriate to create a new test file, e.g. spec/02-integration/05-proxy/32-query-params_spec.lua
.
For this specific change, feel free to use the default output of helpers.each_strategy()
, which won't require extra work to make the dbless
test pass, so that an implementation similar to your first attempt should work just fine.
@samugi Added the test case in a separate file. |
0259c92
to
af1823d
Compare
af1823d
to
c7e197e
Compare
query args that are set in a plugin by kong are not forwarded to the upstream in case of empty query args in request but with a ? (e.g. /route?) also add test to validate the same Fixes Kong#11325
c7e197e
to
76ff95f
Compare
@samugi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
thanks again for your contribution @chirag-manwani! As @oowl also mentioned before I believe there is no plan to backport this right now, but we will update you here if that changes. |
Summary
This PR fixes the issue described in #11325
Checklist
Full changelog
Fix query args handling code introduced in this commit.
Issue reference
Fix #11325