Ged,
Thanks for the input-- here are my answers below...
The new parameter (which in the example was moe and not joe, my mistake)
will be a "webid", a unique identifier for each website that is parsed out
of the physical location of the file.
For example,
www.joe-honda-dealer.com/inventory.jsp
corresponds to something like:
/web/active/honda/joedeal/html/inventory.jsp
where joedeal is the webid.
Instead of having a bunch of identical inventory pages, however, we're
just going to have one JSP on the Weblogic server that accepts a webid
parameter which is responsible for how the page gets built. Let me know if
you need further clarification on this.
My main issue is that I don't know how to add parameters to the POST and
GET data.
Again, thanks for the help!!
Andrew Chen
Software Engineer, Architecture
[EMAIL PROTECTED]
206-219-8445
The Cobalt Group, Inc. (www.cobaltgroup.com)
2200 First Avenue South
Seattle, WA 98134
On Wed, 15 Nov 2000, G.W. Haywood wrote:
> Hi there,
>
> On Tue, 14 Nov 2000, Andrew Chen wrote:
>
> > 1. Request comes in for t.jsp?test=1&joe=2
> > 2. Handler steps in and adds another parameter, t.jsp?test=1&joe=2&moe=3
> > 3. Request is then handled by BEA-Apache bridge so that it is forwarded to
> > Weblogic
> > 4. JSP runs on Weblogic, and the new parameter (joe)
>
> moe?
>
> > can be referenced in the JSP.
>
> I'm not familiar with this bridge, but I don't see why this needs to
> be complicated. What determines the new parameter? After the handler
> adds the new parameter, could you get it to make another request which
> then gets caught by mod_rewrite and/or mod_proxy for example?
>
> 73,
> Ged.
>
