Comment 4 for bug 1688074

I don't know that the expected behavior was ever defined only that it worked a certain way and now it acts a different way. Maybe that is the fundamental problem here, we didn't define the behavior so everyone has their own expectations and we have no good response. Before we make any more changes to the route, we should define this behavior first. That's something to discuss during v6 development.