The benefit is the client is already doing it this way and wants us to it
the same. The realities of the IT world.
Alas...
-Original Message-
From: Ben Souther [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:23 AM
To: Tomcat Users List
Subject: RE: URL mangling
Probably, I
nt: Wednesday, August 22, 2007 9:10 PM
> To: Tomcat Users List
> Subject: RE: URL mangling
>
> Yes, it should.
> Are you running tomcat behind Apache HTTPD or another web server to
> serve up static content?
>
>
>
>
>
>
> On Wed, 2007-08-22 at 09:17
well?
-Original Message-
From: Ben Souther [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 22, 2007 9:10 PM
To: Tomcat Users List
Subject: RE: URL mangling
Yes, it should.
Are you running tomcat behind Apache HTTPD or another web server to
serve up static content?
On Wed, 2007-08-
nd I only get the original one, nothing for the
> images and stuff.
>
>
> -Original Message-
> From: Ben Souther [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 22, 2007 9:03 AM
> To: Tomcat Users List
> Subject: Re: URL mangling
>
> > So now I
AM
To: Tomcat Users List
Subject: Re: URL mangling
> So now I'm trying to see if there's a way to mangle these urls dynamically
> on the security server instead so that I can use the same JSP for
> everything. I tried using a filter, but that works ONLY for the actual
> request itse
> So now I'm trying to see if there's a way to mangle these urls dynamically
> on the security server instead so that I can use the same JSP for
> everything. I tried using a filter, but that works ONLY for the actual
> request itself. Filters evidently don't see requests for images or
> stylesheet
I have two ways of running my webapp. One is your basic webapp where tomcat
answers the responses directly. The second runs security software the
forwards the requests to another tomcat instance. This second version was
mandated by our clients.
The second version is brand new to us and I'm now
