Foren

Tomcat responds "404" to requests for the root document

thumbnail
Mathias Kratzer, geändert vor 12 Jahren.

Tomcat responds "404" to requests for the root document

New Member Beiträge: 17 Beitrittsdatum: 11.10.11 Neueste Beiträge
Hi,

we have a Liferay 6.1-GA1 running on a SuSE Linux Enterprise Server 11. I'm trying to find out why the bundled Tomcat 7.0.23 keeps returning status 404 on requests for http://<hostname>:8080/. In fact, the full response always looks like this:


**** STATUS ****
HTTP/1.1 404 Not Found

**** HEADER ****
Date: Mon, 16 Jan 2012 15:09:44 GMT
Server: Apache-Coyote/1.1
Content-Type: text/html;charset=ISO-8859-1
Set-Cookie: JSESSIONID=C846FE2AD69C8A7F84747BFCCB08E801; Path=/; HttpOnly
Connection: close
Transfer-Encoding: chunked

**** CONTENT ****
2e6














        <title></title>
        <meta content="1; url=/c;jsessionid=C846FE2AD69C8A7F84747BFCCB08E801" http-equiv="refresh">




<!--
The numbers below are used to fill up space so that this works properly in IE.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807 for more
information on why this is necessary.

12345678901234567890123456789012345678901234567890123456789012345678901234567890
12345678901234567890123456789012345678901234567890123456789012345678901234567890
12345678901234567890123456789012345678901234567890123456789012345678901234567890
-->






so if you visit the page with your browser the JavaScript redirect is performed, you are landing on http://<hostname>:8080/home, and everything looks fine. But if a monitoring script (such as Nagios' check_http) sends the request it just receives the error status and issues a warning, of course. How can I configure Tomcat to respond in a way that doesn't suggest any problems?

Thanks in advance
Mathias