I am probably not the first who asks this question, but I still cannot find a solution.
An Ember application is based on:
- Ember CLI 0.2.0-beta.1 - Ember 1.10.0 - Ember Simple Auth 0.8.0-beta.3
The application is deployed on a Tomcat server. When a user traverses through application pages, browser URL changes itself based on defined application routes.
If at some moment the application is in a route, let’s say,
http://my-domain/my-app/one/two/three and a user does browser refresh (F5), then the Tomcat (and not Ember application itself) tries to find the path
one/two/three in the deployed web application and obviously a user gets an error.
I found some advises to set the
locationType property to
hash in Ember CLI config (it was
auto by my side). But the problem does not get resolved with it, and in addition the Ember Simple Auth stops to work.
Has anyone had a positive experience with browser refresh for an Ember CLI application?