You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual results
The deployment works and the resulting /print/ folder contains an index.html-file. If copied to the local drive and opened there, the following shows:
However, if one tries to reach the localhost-link directly, the request for the index.html returns a 404-error.
Seemingly, it is not due to a connectivity issue of the Tomcat itself, as a deployment of the sample war works and http://localhost:8080/sample/ can be reached as expected.
Question
Is this a known issue with older versions of Tomcat (ours is a bit outdated, I know), or what could be the reason for this?
Thank you all for your support and have a nice evening!
Kind regards
Rouven
The text was updated successfully, but these errors were encountered:
Update: It has to do nothing with either the Tomcat version or the mapfish version. We updated to Tomcat 10.1.19 and also tried with the older Mapfish version 3.22.0 to try and apply the solution proposed in issue 1215 (see here).
As before, the Tomcat displays the webapp in its manager pane, but http://localhost:8080/print/ comes back with a 404 error as before.
RouvenZ
changed the title
Index.html not available (404) - possible compatibility issue?
Index.html not available (404) on Tomcat
Feb 27, 2024
Dear all,
sadly, we cannot get our mapfish to work properly.
Context
Describe the bug
The request for the http://localhost:8080/print/index.html fails after deployment, as does the one for http://localhost:8080/print/ folder in general.
How to reproduce
Actual results
The deployment works and the resulting /print/ folder contains an index.html-file. If copied to the local drive and opened there, the following shows:
However, if one tries to reach the localhost-link directly, the request for the index.html returns a 404-error.
Seemingly, it is not due to a connectivity issue of the Tomcat itself, as a deployment of the sample war works and http://localhost:8080/sample/ can be reached as expected.
Question
Is this a known issue with older versions of Tomcat (ours is a bit outdated, I know), or what could be the reason for this?
Thank you all for your support and have a nice evening!
Kind regards
Rouven
The text was updated successfully, but these errors were encountered: