Superfluous trailing '/' added by front end available fs backend links

What steps will reproduce the problem?
1. set up an s3 backend
2. browse the filesystem in the front end.

What is the expected output? What do you see instead?
Should see the filesystem. You get a 404 instead. But only from the available 
backend links. From the header bar in the fileselector window it works.

Basically, the available backends view puts a superfluous '/' on the end of the 
filesystems. The header tab does not. This is fine for most filesystem based 
backends, like POSIX fses, but for key based systems like S3, path/to/file// is 
diferent to /path/to/file/

Original issue reported on code.google.com by retrogra...@gmail.com on 26 Apr 2012 at 3:58

google-code-export / yabi

Superfluous trailing '/' added by front end available fs backend links #195