HELP: apache rewrite rule destroys sessionid for tomcat?

hi ng,

the problem:
our tomcat does not get any information about the used session (sessionid
lost, causes by rewriterule?), when using the apache1 (with a rewriterule to
the apache2). It seems, that the tomcat creates a new session each time,
when a jsp is requested.

It works, when we are directly using the apache2.

Request --> apache1(rewriterule) --> apache2(Bridge) --> tomcat

we are using an apache 1.3.27 and a tomcat 4.1. The tomcat is included into
the apache with mod_jk2, using the following params in workers2 (Apache2):
[logger]
level=DEBUG
[config:]
file=/etc/httpd/conf/workers2.properties
debug=1
debugEnv=0
[uriMap:]
info=Maps the requests
debug=1
[channel.socket:xxx.xxx.xxx.xxx:8009]
info=Ajp13 forwarding over socket
tomcatId=xxx.xxx.xxx.xxx:8009
[uri:/etz/*]
#worker=ajp13:xxx.xxx.xxx.xxx:8009
info=Application
[shm:]
info=Scoreboard
file=/etc/httpd/logs/jk2.shm
size=100000
debug=0
disabled=0


Our rewrite rule in httpd.conf (Apache1):
<IfModule mod_proxy.c>
NoCache *
ProxyRequests On
RewriteEngine On
RewriteLog /var/log/httpd/rewrite_log
RewriteLogLevel 3
RewriteRule ^/pms/(.*)$ http://ourserver/$1 [P,L]
</IfModule>


thanks for answers
Frank

Frank <Frank.Martens_no!spamx!xmm@bertelsmann.de> wrote:
 > our tomcat does not get any information about the used session (sessionid
 > lost, causes by rewriterule?

Usually sessions are kept using cookies or (less common) sessionid on the
URL. If you are using the latter, be sure to preserve the session id.
It's time for you to do some debugging about what kind of sessionid
is used by your application and if there are problems in preserving
those info.

Davide

--
| But officer, I was only trying to gain enough speed so I could coast
| to the nearest gas station.
|
|<!-- ~MESSAGE_AFTER~ -->