direct port to 80

[Edgar Trania, modificado hace 11 años.]

hi guys i know it would be bad design but what are the disadvantages if i direct(no apache httpd) use tomcat server port to 80

[David H Nebinger, modificado hace 11 años.]

No first tier caching of static resources. No taking advantage of many of the modules Apache provides. Etc.

It's not that it's bad design per se. You can operate tomcat off of port 80, it's just that it's not tuned to serve static resources in the same way a standard httpd server is.

[Edgar Trania, modificado hace 11 años.]

that is noted.. tnx so much for reply

[Hitoshi Ozawa, modificado hace 11 años.]

Many sites use up front httpd to route traffic to clustered backend liferay servers.

There's also may be some security risk with setting application server to run on port 80. Why don't you just let application server run on port 8080 and setup iptable to forward traffic from port 80.

[Olaf Kock, modificado hace 11 años.]

Agreed and preferred (in case you really want to go without Apache).

The easiest way to bind tomcat to port 80 on Unix-flavoured boxes is to run as root - that certainly is a bad idea, don't do that.

By the way, my favourite killerfeature for Apache httpd in front of tomcat even on small installations is mod_rewrite. Sometimes it's easy to bugfix/rewrite on the webserver level. Saved me lots of work when I didn't have time for a proper solution in the backend.