I run ZoneAlarm sw firewall, which I have configured to allow client connections to Tomcat server. And port 8080 is getting through, and my version of ZoneAlarm filters only on IP address, not the full socket. However, your comments remind me that I have another sw firewall as part of my corporate VPN client. It's a squirly one, and I'll bet it's causing the problem. I'll disable it and try the HTTPS session again.
I have to go to work to test it, and hopefully my wife won't shut down my computer while I'm at work as she did yesterday. :)
Thanks for your suggestion.
Peter Crowther wrote:
[Marked as OT because not Tomcat-specific]
From: Mark Leone [mailto:[EMAIL PROTECTED] I have Tomcat 5.5.7 behind a router/firewall, with port 443 and 8080 forwarded through the firewall. I can make connections from outside the firewall to port 8080, but not port 443 (it times out). I can access port 443 on my server if I browse to my server's LAN address or if I browse to my router's WAN address (i.e. loopback mode).
That feels like a firewall config problem - are there any input filters on the WAN interface that are preventing 443 from ever being accepted from an external address? That would give the behaviour you describe. As for the ISP filtering 443, that would be very unusual. Can you test by putting another computer on the outside of the firewall with an appropriate address?
My ISP blocks some ports, but not 443. What port is used for the server response to a request made on port 443? Is it also 443 or something else. I'm wondering if my ISP is blocking it.
It's 443. HTTP and HTTPS are well-behaved protocols, unlike nasty stuff like FTP in active mode.
- Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
