× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Fri, 2004-03-05 at 18:23, Joe Pluta wrote:
> The biggest problem in your case is that typically requests come in on
> port 80, not port 8080.  You will either have to use
> http://www.domain.net:8080 to access your machine, or you will have to
> set up Tomcat to listen on port 80 rather than 8080.  I personally don't
> know of any routers that do port mapping as well, though someone more
> versed in this subject could certainly help.  And my guess is they are
> likely to reside on WEB400-L (or perhaps even MIDRANGE-L).
> 
> Joe

Unless you are trying to protect your server from random access, I would
recommend port 80.  And be aware that changing the port is only security
by obscurity.  If you do need protection, look into .htaccess or
"AuthUserFile/Require valid-user" (Apache Configuration).

I'm guessing though that the reason you have 8080 is because that is the
default Tomcat install, I'm sure for testing purposes.  And yes, this
should probably be shifted to Web400-L.

Joel
http://www.rpgnext.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.