this maps to "tracks/1", "tracks/" (notice the trailing slash) AND (surprisingly enough) to "tracks".
I've noticed that when the router tries to resolve "tracks/" (with a trailing slash) the router redirects to "tracks" (without the trailing slash) when in my opinion it should redirect to a 404 page, given that it didn't find the resource (in this case the id is empty since there's nothing after the trailing slash).
When adding the following route :
this maps to "tracks/1", "tracks/" (notice the trailing slash) AND (surprisingly enough) to "tracks". I've noticed that when the router tries to resolve "tracks/" (with a trailing slash) the router redirects to "tracks" (without the trailing slash) when in my opinion it should redirect to a 404 page, given that it didn't find the resource (in this case the id is empty since there's nothing after the trailing slash).
What are your thoughts on this ?