Re: forwarding to a remote host

lt;[EMAIL PROTECTED]> > To: "Tomcat Users List" > Sent: Tuesday, July 11, 2006 14:38 > Subject: Re: forwarding to a remote host > > >> Zohar, >> - In the same host & context, use RequestDispatcher.forward() >> - In the same host but different cont

Re: forwarding to a remote host

What's the easiest way to transfer all the data from the Request to the PostMethod? - Original Message - From: "Avi Deitcher" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Tuesday, July 11, 2006 14:38 Subject: Re: forwarding to a remote host Zoha

Re: forwarding to a remote host

Yeah, that is a good point. The third option - cross context disabled or remote host - will not keep session data, unless you one of three things: - the request is stateless (where it doesn't matter anyways) - you forward everything to the remote host, including the cookies and all; this seems comp

Re: forwarding to a remote host

Hi Zohar Check this http://marc.theaimsgroup.com/?l=tomcat-user&m=108568149602563&w=2 Hope this helps - Regards Vinu Zohar wrote: Hello list, I have a servlet that handles POST requests. Sometimes the request needs to be f

Re: forwarding to a remote host

not unless you've got clustering setup and the cluster is correctly sharing session data. the session data is otherwise local to the server in use. Vinu Varghese wrote: > Avi, > What will happen with the session and objects bound to it ?, Will they > be accessible in the second server ? > > - Re

Re: forwarding to a remote host

Avi, What will happen with the session and objects bound to it ?, Will they be accessible in the second server ? - Regards Vinu Avi Deitcher wrote: Zohar, - In the same host & context, use RequestDispatcher.forward() - In the same host but different context, if cross-context enabled, get the

Re: forwarding to a remote host

Zohar, - In the same host & context, use RequestDispatcher.forward() - In the same host but different context, if cross-context enabled, get the RequestDispatcher for that context then use forward() - Different host entirely, or cross-context not enabled, you will probably need to rebuild the reque