Assuming I have some simple routes in my Ember app ...
MyApp.Router.map(function () {
this.resource('myresource', { path: '/' }, function () {
this.route('myroute', { path: '/home/myroute' });
});
});
The router on my server side is case insensitive, so when the end user blocking the lock lock activates the types "WWW.BLAH.COM/HOME/MYROUTE" in his browser, my server responds to the page that the Ember application launches, but after rendering Ember explodes because there is no such route (Ember seems to take care of the incident along the way).
I'm curious ... is it in design, and is there anything that can be done about this? I'm struggling to figure out why Amber cares about this case. Is this related to the dynamic parts of the URL (which are not used in this case)?
Note. I noticed this question that discusses the same issue in AngularJS. If there was something similar in Ember, I think this will solve my problem here.
source
share