If the provided url is url-encoded (as it should), the route won't work if the parameter receive data with special characters.
For example, to pass "hello world" and "1 + 1 = 2" in paramA and paramB, respectively, the url could be:
/a/b/hello+world/1+%2B+1+%3D+2
The methods defining the routes here receive the data non-decoded, i.e. "hello+world" is received in the parameter rather than "hello world".
The static files having a pattern with parameters containing special characters also do not work, and I suppose that it is related to the same issue.
I had a route defined by a pattern such as
If the provided url is url-encoded (as it should), the route won't work if the parameter receive data with special characters. For example, to pass "hello world" and "1 + 1 = 2" in paramA and paramB, respectively, the url could be:
The methods defining the routes here receive the data non-decoded, i.e. "hello+world" is received in the parameter rather than "hello world".
The static files having a pattern with parameters containing special characters also do not work, and I suppose that it is related to the same issue.
Here is a test:
Query (here the + means a space):
Result: