Locations: Support trailing /

[mathiasbn]

At the moment you cannot create hrefs from a location with trailing /:
/somepath/ as it would end up being /somepath

This should of cause also work for nested Locations, so i could do:

@location("/somepath/") class SomeLocation{
    @location("/nested/") class Nested
}

and get /somepath/and /somepath/nested/

[gzoritchak]

I agree. Having the trailing / or not is considered as two different urls. It could serve (even if it is not recommended) 2 different contents.
http://webmasters.stackexchange.com/questions/68721/in-terms-of-seo-what-is-the-difference-between-a-url-with-and-without-a-trailin

I have the same problem as @mathiasbn. An older website I plan to migrate have urls with the trailing /. It would be easier to do the migration with locations managing it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity.

[hhariri]

For follow-ups to this issue, please see https://youtrack.jetbrains.com/issue/KTOR-836

[oleg-larshin]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.