Getting decoded request path parameter

[lynshi]

Is your feature request related to a problem? Please describe.
We talked about this in a previous email thread but since it didn't come out in 2.0.5 we might've lost track of it, so creating an issue just in case (I also didn't find an existing issue)! As discussed, the current code

• URL decodes queries
• URL decodes fragments

It does not

• URL decode the path before dispatch
  • So "/foo bar" and "/foo%20bar" are two different endpoints
• URL decode the path params after dispatch

This is believed to be intentional because of https://github.com/microsoft/CCF/blob/main/src/http/test/http_test.cpp#L393.

Describe the solution you'd like
While normalizing paths for dispatch could be a topic for future discussion, a more immediately useful method would be one like get_decoded_request_path_parms(), which returns URL-decoded path parameters (unlike the existing get_path_param(), which will return the path parameter, encoded).

Describe alternatives you've considered
Currently the application must explicitly do the decoding after fetching path parameters.