Routes should urldecode their parts
requesting the following Flow project URI, for example,
results in a resolved controllerName of
foo%62ar while it should of course be
This is incorrect by reading; and especially problematic in sub-namespaced controllers like even in nativ Neos' Backend\BackendController (however in this case it's circumvented by a custom route).
Such a controller would be
intended to result in an controllerName of
Updated by Adrian Föder almost 9 years ago
..the question is whether to decode the whole query string pretty early, making
which could be unwanted, for example in this case:
this is surely intended to result the title representation
The Wizard of Oz/Wonderful wizard of Oz
so I think the decoding should take place "later" on the value of the route part.
Updated by Bastian Waidelich over 8 years ago
- Status changed from New to Needs Feedback
- Priority changed from Must have to Should have
I'm not so sure about this one. We should definitely not decode the complete request path (btw. you mix up query string with request path, for the query string it might be different) because that would prevent you from having dynamic RouteParts containing a slash for instance.
I wonder in what cases you end up with the urlencoded version? I suppose this is a problem with "Object routing". The IdentityRoutePart-Handler should probably de/encode the part!