Issue #352: SSH does not ingore trailing slash(es) in repo names (conservancy/kallithea)

[lns_ross]

New issue 352: SSH does not ingore trailing slash(es) in repo names
https://bitbucket.org/conservancy/kallithea/issues/352/ssh-does-not-ingore-trailing-slash-es-in

Ross Thomas:

When a repo is presented to the Kallithea SSH service with one or more trailing slashes \(/\) it fails to recognize the repo.

This was highlighted by a bug in the mercurial ‘schemes’ extension where a repo ref that only has a single path component will generate a repo name with a trailing slash.

The 'schemes' extension is not needed to reproduce, just add a slash to the end of a working SSH repo ref.  For example,

`$ hg in ssh://…/working-repo`

works, but this doesn’t:

`$ hg in ssh://…/working-repo/`

Other SSH services I’ve tried \(and obviously https-based ones\) ignore the trailing slash\(es\).

Kallithea version: 0.5.1 \(also in 0.5.0\)