-
Notifications
You must be signed in to change notification settings - Fork 128
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
Handling of 'multiValueQuery' not respecting encoded characters #277
Comments
Hey @vandrade-git, Wdyt making this a configurable option? |
Hi @naorpeled I don't mind creating a PR to address this although I am not sure how being configurable would work in this case. Is your idea something similar to the 'serializer' configuration option? |
exactly, and I'd call it something like what do you think? |
After heavy testing looking for a solution I realized that everything in lambda-api is working correctly. |
Alrighty, if you need anything else feel free to ping me 🙏 |
When trying to handle multiple query parameters with encoded characters, the decoding is done before the split resulting in some weird behavior.
My example is the encoding of commas.
Looking at the source I can see the logic that explains why this is happening:
Is this the intended behavior or a strange edge case?
The text was updated successfully, but these errors were encountered: