Forum Moderators: phranque

Message Too Old, No Replies

Apache - Bea module redirect

Apache redirect to BEA is failing when the URL has parameters in it.

         

kalevoor

3:59 pm on Aug 31, 2006 (gmt 0)

10+ Year Member



Hello,

We are using Apache 2.0.58 from apache.org.
Added Bea weblogic module to http.conf for Apache to redirect anything with "test" in the url to Bea weblogic - on a different server.

<<<<<<<<<< part of http.conf >>>>>>>>>>>>>>>
LoadModule weblogic_module modules/mod_wl_20.so
#BEA Application.
<Location /test>
SetHandler weblogic-handler
WebLogicHost localhost
WebLogicPort 8001
SetHandler weblogic-handler
</Location>

Everything gets redirected and is working great... but when it encounters a .jsp page which creates parameters to be passed to the url (see URL Eg. below) it fails with error: "Page cannot be displayed".
<<<<<<<<<<<<<< URL Eg. <<<<<<<<<<<<<<<<<<
URL - [appserv:8001...]

Note that this app runs fine on just BEA framework.
So am I missing something in the configuration to re-direct? Why is it failing just on the dynamically created URL parameters?

Thanks!

jdMorgan

4:07 pm on Aug 31, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Without seeing your redirect code (mod_alias or mod_rewrite) it's hard to tell...

Just be aware that query strings are usually handled separately, since they are data attached to a URL to be passed to the resource *at* that URL.

Jim

kalevoor

4:20 pm on Aug 31, 2006 (gmt 0)

10+ Year Member



Thanks Jim!

Where would I find the file with the redirect code.
Are you refering to c:/<APACHE-HOME>/modules/mod_alias.so & mod_rewrite.so

Also since most part of the redirect is working fine, how do I go about specifying the way to handle query strings?

Thanks!
Kavitha

kalevoor

10:03 pm on Aug 31, 2006 (gmt 0)

10+ Year Member



Well... we figured it out.
Had nothing to do with Apache. It was the BEA configuration.

But Thanks to one of the threads in this forum... I discovered that our server was throwing - page cannot be displayed when I typed the application context root without the "/".
Resolving this issue automatically resolved the other one!

Thanks!