Link to "/" with basename adds extra trailing slash

Version

4.2.0

Test Case

https://codesandbox.io/s/6llwm7m8zz

Steps to reproduce

<BrowserRouter basename="/foo/bar">
    <Route path="/" component={App}/>
</BrowserRouter>

<Link to="/" />

Expected vs. Actual Behavior

the link takes me to http://host/foo/bar/ (with trailing slash) when I expect http://host/foo/bar (without trailing slash)

[ajenkins-kyr]

Is there any way to get the behavior that @mmartha is looking for using basename without implementing some kind of redirect behavior? This seems like a very normal use case and I can’t figure out a working solution other than not using basename altogether.

[mmartha]

thanks @timdorr, I’ve implemented a server side redirect as a workaround, looks like I’ll just stick with that!

Do you have any explanation or link to a discussion thread for why this was decided to be the expected behavior? It doesn’t seem ideal since the root route is a file rather than a directory. Additionally, it seems strange that the root route’s behavior (wrt trailing slash) would differ when using basename vs. when not.