404 page not found error without specifying port 8080 tomcat
Hello,
We experienced an unexpected tomcat down, after restarting it no page is found if 8080 port isn磘 specified, in the past it wasn磘 needed.
What could be causing that behavior?
I went to the server.xml file and everything is in order:
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector port="8080"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" />
Thanks!
# 1
If you don't specify a port number in an HTTP URL, then port 80 is assumed. But you posted something that says (or it looks like that to me) that Tomcat is configured to listen on port 8080. So what could be causing that behaviour? It's by design.
The real question is why Tomcat was listening on port 80 before you did the restart. My guess would be that the server.xml file was edited after it was last started.
# 3
> So, how can I force all requests to be responded by
> the 8080 port without specifying it?
If you don't specify the port on an HTTP URL then the request is sent to port 80. (This is part of the HTTP standard which is used on every computer in the world, it would be difficult for you to get that changed.) So applications listening to port 8080 will not hear those requests. I suppose you could run a port mapper or something but it would be more practical for you to just learn how things work instead of trying to bend them all out of shape to work the way you guessed they might work.
> Should I comment the snippet for the 8080 port so 80
> responds to all requests?
If it were me I would change the attribute to read port="80", if you really want your server to listen at port 80. That element configures a whole lot of other properties and you don't want to just throw that configuration away.
