Basically, I'm not--currently. It definitely doesn't handle it correctly, just as you described. I'll likely make it a property on the App.Router and then have all location classes honor it.

These catches are exactly what we need right now so thank you very much for reporting! Keep'um coming.