problems with 8080

i'm having a bit of a curious (i.e., bad) problem, and i was wondering if anyone had any advice...

i have a linux box with tomcat and apache off a dedicated server at the planet. my application runs off of tomcat (i use struts for a framework), and overall everything seems to run well. i've been able to access the website from a variety of different locations (including home, friends' homes, internet cafes in europe, etc.).

however, i once went to a cafe here in boston with free wireless internet access, and i wasn't able to get to the site. after doing some poking with telnet, i discovered that i *was* getting the initial page from the apache server (the sole purpose of which is to redirect to the tomcat server), but that it wasn't getting anything when it requested the page it was redirected to. the only thing i could think of is that the cafe had some kind of filter up that didn't allow requests to port 8080, and i ended up ignoring the problem.

unfortunately, a contractor has just had the same problem from her home (cable modem). she's being redirected to port 8080 (correctly), but then it can't find the page.

does this ring any bells? any solutions?

daniel

p.s. i've noticed that it's rare to actually see ":8080" in a URL. (e.g., http://java.sun.com/index.jsp). is there a canonical way to do this? (do they just set their container to use port 80?)

 

 

 

 

Top