-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Illusion,

illusion wrote:
| I tried taking the address="192..." portion out in the example 2 where
| tomcat is behind a router and it made no difference.  In relation to
port 80
| being blocked, in example 1 above where there is no router, it works fine
| when tested with the url with the ip address assigned by the ISP,
| "http://99.....";, so port 80 is not being blocked.

If you really are talking about a router (and not a proxy, as Chuck
suggests), have you set up your router to forward requests to port 80 to
go to your internal IP address (192.168.0.54)? If not, there's no reason
to expect your router to automagically forward port 80 traffic to one
specific machine on your internal network.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhRrAUACgkQ9CaO5/Lv0PDNuwCguS7M60B1pIYsjM/2wTD9fcNm
yDoAnjVoQi0pBGqThx4wAKR2wACJjx/m
=OI9K
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to