Okay, you are trying to perform a forward from one server to another. Well the most easy option is to use a 306 but as you stated, you don't want to use any header redirects (though all conformant browsers accept these). Your next option is to reroute the messages from your server to another server and let that server decide what to do (this is what's called a proxy). The only thing the first server is doing is being sheepish.
Using this technique as I explained below, you can redirect cross-server, or if you want, cross-application without the need for the browser to know what's going on. Making a proxy can be done in all kinds of manners, one of them should probably fit your needs.
A third option, which is usable with large scaled applications, is to use node systems, but this is only necessary for huge systems.


If there is a question regarding to proxying do not hesitate to ask.

Regards,
Sjoerd

Sreejith wrote:

Thanks for the reply Sjoerd..

I am trying to write a framework over Tomcat, which can be used to manage
the web apps.
The framework maintains certain access levels based on the request data
(from client). Following certains buisness rules, framework does forwarding
(server side, using req Despatcher) to the appropriate web apps. In certain
scenarios, it may be required to redirect to a third party (remotely hosted)
web application. Can you tellme, what is the best approach to implement this
with out using 3xx response codes?

Thanks
Sreejith

-----Original Message-----
From: Sjoerd van Leent [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 08, 2004 4:41 PM
To: Tomcat Users List
Subject: Re: Server side redirect


Sreejith wrote:



Hi all,
  It is possible to do a server side redirect to another Tomcat Server
(any other web server)? I dont want to use status codes 3xx, as this
involves the user agent in redirection.

Sreejith




What you are asking is to locate a resource on another server. If you
want to do this you need to route the request to another server (setting
tomcat as a proxy). You are more or less making the server the
browser-client is talking to another client of a deeper server. More or
less like the following illustration:

   browser ------> tomcat ------> another tomcat

In most cases it would be more wise to setup another webserver (such as
apache) that routes your requests to different tomcat servers (using the
mod_jk extension or something like that), which looks more like the
following:

                                               ------> first tomcat
   browser ------> proxy (apache for instance) ------> second tomcat
                                               ------> third tomcat

May I ask what you are actually trying to do?

Regards,
Sjoerd


--------------------------------------------------------------------- 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]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to