That's true of mod_jk in j-t-c. At least through B2 the mod_jk that ships
with 3.3 uses r->uri.
----- Original Message -----
From: "Keith Wannamaker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 12, 2001 12:11 PM
Subject: RE: Remaining Tomcat 3.3 Issues
> mod_jk uses (used?) r->unparsed_uri to preserve encoding.
> Therefore, any mod_rewrite munging of r->uri is invisible
> to mod_jk. This is the issue to which Larry is referring,
> not Apache module ordering.
>
> Keith
>
> | -----Original Message-----
> | From: Bill Barker [mailto:[EMAIL PROTECTED]]
> | Sent: Wednesday, September 12, 2001 2:30 PM
> | To: [EMAIL PROTECTED]
> | Subject: Re: Remaining Tomcat 3.3 Issues
> |
> |
> | Re. 11) I use mod_rewrite + mod_jk regularly without problems. The
problem
> | is that the "out-of-the-box" model order puts mod_jk ahead of
mod_rewrite.
> | The trick to make them play happily together is to simply re-order them
in
> | httpd.conf. Of course, this has the downside that you can't use the
file
> | generated by ApacheConfig verbatim. But if you want advanced
functionality,
> | you have to expect to fiddle with the configuration.
>
>
*----*
This message is intended only for the use of the person(s) listed above
as the intended recipient(s), and may contain information that is
PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
you may not read, copy, or distribute this message or any attachment.
If you received this communication in error, please notify us immediately
by e-mail and then delete all copies of this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent
through the Internet is not secure. Do not send confidential or sensitive
information, such as social security numbers, account numbers, personal
identification numbers and passwords, to us via ordinary (unencrypted)
e-mail.
