/Tomcat6.0.13] redirect url problem
Since you want to do an internal URL rewriting, it doesn't make much
sense to me, to use a full URL including protocol and host. I would try
the line, you commented out, instead. I guess, that you already tried that.
You should definitely see log entries in the rewrite
I am trying to migrate our current system of apache/jserv to apache tomcat
using modjk. I am trying to shoe horn our current configuration.
I have a webapp lets call it myApp. Now some of our static content, beyond
my control, requests urls like
Hi Dan,
OK, two problems here:
1) URL encoded session ids and forwarding. I assume you are using mod_jk
1.2.23. For this problem you already found a workaround, although the
JkOption is not really safe. This topi will be fixed in a nicer way in
the forthcoming version 1.2.24. The reason you
=myApp debug=0
reloadable=true /
Two separate webapps = a session headache.
Unless I am missing something...
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 24, 2007 11:35 AM
To: Tomcat Users List
Subject: Re: [Apache2.2.4/modjk/Tomcat6.0.13] redirect url
You can do this with mod_rewrite. Don't forget to use the PT flag, when
combining mod_rewrite and mod_jk.
If it doesn't easily work for you:
Add a RewriteLog with a high RewriteLogLevel (e.g. 9) and increase
JkLogLevel to debug. Then you can follow the manipulation of the URL.
Regards,
-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 24, 2007 4:42 PM
To: Tomcat Users List
Subject: Re: [Apache2.2.4/modjk/Tomcat6.0.13] redirect url problem
You can do this with mod_rewrite. Don't forget to use the PT flag, when
combining mod_rewrite and mod_jk.
If it doesn't
Since you want to do an internal URL rewriting, it doesn't make much
sense to me, to use a full URL including protocol and host. I would try
the line, you commented out, instead. I guess, that you already tried that.
You should definitely see log entries in the rewrite log, if the module
is
