I understand that turbine treats them the same, but I think the other
components don't handle these the same, thus this only matters on
redirect.

A request like this

http://apache-server/app/servlet/app/action/blah?param1=foo&param2=bar

gets re-written on redirect as

http://apache-server/app/servlet/app/param1/foo/action/blah/param2/bar

and it appears that apache does not pass this on to the servlet, and
returns a 404. (remember I'm using apache and mod_jk)

Now if I hack the servlet to use setQueryData instead of setPathInfo in
the redirect code, the url is rewritten as

http://apache-server/app/servlet/app?action=blah&param1=foo&param2=bar

and apache passes on the redirect. I assume that apache or mod_jk is
getting confused by the app/servlet/app/param1/foo part.


>-----Original Message-----
>From: John McNally [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, August 07, 2001 10:20 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Redirect / PathInfo problem
>
>
>Turbine treats PathInfo and QueryData the same, so it should make no
>difference.  How is the redirect request getting mangled?
>
>john mcnally
>
>Chris Campbell wrote:
>> 
>> I've discovered a problem with my Apache-WebLogic-Turbine(2.1b) setup
>> and I'm not sure if it is a problem with Turbine or not.
>> 
>> The problem occurs on a the first request when there is a redirect.
>> Turbine writes parameters from the request into the PathInfo, even if
>> the parameters were originally in QueryData. The redirect 
>path is a bit
>> mangled, and apache returns a 404. If I change the Turbine servlet to
>> put parameters into query data instead, apache does not get 
>confused. I
>> don't know if this is a mod_jk bug or a weblogic bug or a 
>Turbine bug...
>> 
>> Does anybody know why Turbine puts parameters in pathinfo instead of
>> querydata on redirect?
>> 
>> Thanks,
>> Chris
>> 
>> ---------------------------------------------------------------------
>> 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