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

Empty parameters not forwarded, blocker for me #1209

Closed
JnMik opened this issue May 13, 2016 · 1 comment
Closed

Empty parameters not forwarded, blocker for me #1209

JnMik opened this issue May 13, 2016 · 1 comment
Assignees
Labels

Comments

@JnMik
Copy link

JnMik commented May 13, 2016

We are using a third-party system API and we can lookup for data by searching for fields with empty values doing so :

&filters%5Bsome-field%5D%5Bconditional%5D=NOT_EQUAL_TO
&filters%5Bsome-field3%5D%5Bvalues%5D=

See that &filters[some-field][values] is passed but empty.

Our third-party receive the request like this :

"some-field": {
"conditional": "NOT_EQUAL_TO",
"values": ""
},

When using kong, our third party receive the request like this :

"some-field": {
"conditional": "NOT_EQUAL_TO"
},

Seems like the gateway don't feel the need to forward empty parameters, but there is a difference between an empty parameter and an undefined parameter.

Was that a known bug or an expected behavior ?
I would really appreciate having this fixed but i've never done any Lua before.
Thx !

@subnetmarco
Copy link
Member

I just pushed a fix for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants