jeudi 19 février 2015

Ember CLI / browser refresh / production / 404

I developed my webapp using Ember CLI 0.1.15, with emberjs. 1.8.1


I built the app with this command: ember build --environment production , and then I made a WAR out of the files produced under the dist folder of my project, and then I drop the WAR on my tomcat's webapps folder.


So, when I open the app: http://mytomcat/myapp/ ... it went fine, I saw my login screen, I logged in, and navigate around in my app, everythings fine. I could also do the back/forward button, and ember handles the transition well.


But when I click the refresh button on my browser -- the address bar of the browser was showing http://mytomcat/myapp/inventory/ at that moment -- I got 404 reply, from the tomcat.


Then I figured out why it happened: the refresh button sends a request to the tomcat for the path /myapp/myinventory/ ... of course the path /myinventory does not exist on the server. All those routes we see on the browser -- except for the base url, http://mytomcat/myapp/ -- are generated on the client-side.


So, my question is: what's the right way (in ember) to deal with this situation? I need the refresh button to just works. Any way for ember to intercept the refresh button clicked event?


I guess this issues is related to this: http://ift.tt/1vLFj8D , but it does not have the answer I need.


Thanks in advance, Raka


--- UPDATE ---


Probably relevant: http://ift.tt/1hpNLqh





Aucun commentaire:

Enregistrer un commentaire