Although I am not responsible for the front end, I seem to recall we use
mod_proxy for the reverse proxy. We have front end Apache web servers
that listen for requests externally, internally I can access Tomcat
directly. mod_rewrite is used to make our applications on Tomcat and
Apache appear as one.
I use a Java Servlet on Tomcat 5.5.20 with JDK 6.02 ... What I am
curious to know is if the cookie gets set correctly with this
configuration? could the proxy be interfering with normal Tomcat operation?
Is your webapp using a session cookie (JSESSIONID)?
I don't explicitly do anything, Tomcat handles this, but yes.
Peter
Rainer Jung wrote:
Hi Peter,
Peter Stavrinides wrote:
Hi all
My question involves Tomcat in conjunction with Apache and
mod_rewrite. Tomcat appends a jsessionid to the first request, but
not to subsequent requests, which is normal behaviour. When I access
my Servlet directly through Tomcat that is precisely what I get.
But when I redirect requests through Apache and mod_rewrite for some
reason the session id is being appended to every subsequent request.
I can remove this of course using a filter, but before I do so, can
anyone explain to me why this is happening?
What do you mean by "redirect requests through"? Are you using
mod_proxy or mod_jk? You should describe your setup (abstract,
versions used and relevant parts of the configuration).
Is your webapp using a session cookie (JSESSIONID)?
Thanks
Peter
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
