The decoding that takes place in parse() happens too late, leading to encoded '?', '&' and '=' signs not being interpreted correctly:
VERSION:
6.13.1
ACTUAL RESULT:
parse(?key1=value1&key2=value2) returns: {"key1":"value1","key2":"value2"}
parse(%3Fkey1%3Dvalue1%26key2%3Dvalue2) returns: {"?key1=value1&key2=value2":null}
EXPECTED RESULT:
parse(?key1=value1&key2=value2) returns: {"key1":"value1","key2":"value2"}
parse(%3Fkey1%3Dvalue1%26key2%3Dvalue2) returns: {"key1":"value1","key2":"value2"}
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too