-
Notifications
You must be signed in to change notification settings - Fork 71
Open
Description
I'm struggling with Tomcat 8.0.32 and Play 2.4.x, but only in the production server! Locally, the same environment works like a charm.
In particular, when I deploy as ROOT.war, production's tomcat is unable to route the URLs and returns 404. For instance, the first access redirects from index to /login, but it returns 404 instead of the corresponding view.
Now, the weird facts: if I deploy to a sub-context instead of ROOT.war (for instance, app.war), the routing works. Unfortunately this is not a option since reverse routing is bugged in Play 2.4 in sub-contexts (playframework/playframework#4977).
Again, locally everything works. I'm using the same version of tomcat in both enviroments, the same .xml's (differing only in the ports). Any tip?
Metadata
Metadata
Assignees
Labels
No labels