Closed marrony closed 1 year ago
Thanks! This is a legitimate bug we introduced when refactoring the way we manage argument extraction. A fix is in PR (https://github.com/etr/libhttpserver/pull/326)
This should be fixed now on head. Let me know if you still have the problem (and feel free to reopen in case).
Prerequisites
Description
Looks like it's not possible to get querystring arguments when using parameterized paths. If it's not possible, is it documented somewhere?
Steps to Reproduce
Here is a modified version of https://github.com/etr/libhttpserver/#example-of-handler-reading-arguments-from-a-request.
Querying with Simple path + Querystrings:
Logged:
Querying with Parameterized path +
application/x-www-form-urlencoded
:Logged:
Querying with Parameterized path + Querystring:
Logged:
I was expecting to see
Query Args [id:["1"] name:["John"] ]
Looks like it works with
application/x-www-form-urlencoded
data but not with querystring parameters.The documentation says:
How do I get the parsed querystring values when using path arguments?
Versions