tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erin Dalzell <>
Subject RE: Tomcat not working behind a NAT?
Date Sat, 26 Jul 2003 00:15:28 GMT
Well, something is getting out far enough for the NAT to swallow it!

I have managed to upgrade our app to Tomcat 4.0.6 and I will turn up the
debugging info and then trace through the code to learn more about it.

All we do is call a JSP. And that is it. But somehow, the NAT doesn't like



Erin Dalzell
eXpresso Product Specialist
Epic Data

-----Original Message-----
From: Tim Funk []
Sent: Friday, July 25, 2003 4:49 PM
To: Tomcat Users List
Subject: Re: Tomcat not working behind a NAT?

No, forward is an internal forward. It does not leave the JVM. In fact, it 
doesn't leave the servlet context.


Erin Dalzell wrote:
> OK, I have a question for all the Tomcat gurus out there.
> Here is my scenario:
>   	* tomcat machine is behind NAT
> 	* internal ip address is (ip changed to protect the
> innocent!)
> 	* external ip is
> 	* client accesses servlet with ip
> 		* inside servlet we call RequestDispatcher rd =
> getServletContext().getRequestDispatcher( "/another_page.jsp" );
> 		* then we call rd.forward( orig_request, response );
> My question is, is that forward call a full http request? If so, what ip
> address will it use? I "think" that it is trying to use the
> and the NAT doesn't like it.
> Thoughts?

To unsubscribe, e-mail:
For additional commands, e-mail:

This email and any attachments are intended only for use by the addressees
named in this email and may contain legally privileged and/or confidential
information.  If you are not the intended recipient of this email, you are
hereby notified that any use, dissemination, distribution or copying of this
e-mail or any attachments is strictly prohibited.  If you have received this
email in error, please immediately notify me by return email and by phone at
604-273-9146, permanently delete the original and any copy of this email and
any attachments from your systems and destroy any printouts of them.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message