-
Notifications
You must be signed in to change notification settings - Fork 91
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
Setting to do automatic unescaping on request params and query params #59
Comments
Thanks for reporting this. Unfortunately, it's hard to predict when we can address it. |
No problems - understood. |
Hi, @seghcder! |
I just checked two instances where I had issues in the past (param and query) and it seems to be working correctly now. One issue I had was using quote marks in query string like this -
I was thinking to have two paths depending if it was a string name or a numeric ID, but needing to handle the edge case where a name is numeric. At the time it wasn't decoding to "21". But its an edge case, it seems to be working now, and I think there may also have been some issues with the way Postman and/or nginx was processing the url too. I solved it another way in the end but might come back to this topic. If it comes up again will let you know. Feel free to close. |
Ok. |
Suggested feature.
Ie to avoid having to do this for each parameter:
The text was updated successfully, but these errors were encountered: