in reply to Cool uses for path_info

Seems to me that when a new route is added, the default should be that path_info exactly match the route. Otherwise, either supply the route as a regex, or supply an optional parameter which is a regex for matching acceptable additional path_info content. If either the route regex or the additional regex failed to match, then the try the next route.

Either way, path_info would be validated before it was available to any handler.

Replies are listed 'Best First'.
Re^2: Cool uses for path_info
by Dallaylaen (Chaplain) on Nov 29, 2016 at 01:31 UTC

    Maybe I wasn't clear enough, I meant path_info() to be the part of path after the matched route (which I refer to as script_name, following the CGI specification more or less), not including the matched route.

    That said, I did it exactly as you suggested.