On Sat, 31 May 2008 19:16:35 -0700
"Jacob Mathew" <[EMAIL PROTECTED]> wrote:
> Yes the ProxyHTMLExtended directive can, but the ProxyHTMLURLMap
> directive can't. I think I said as much in the line "The solution
> proffered seem to be to use ProxyHTMLExtended and identify the URL
> using regular e
Yes the ProxyHTMLExtended directive can, but the ProxyHTMLURLMap
directive can't. I think I said as much in the line "The solution
proffered seem to be to use ProxyHTMLExtended and identify the URL
using regular expressions. "
My concern is that it is using brute force regular expression
matching,
On Fri, 30 May 2008 08:17:22 -0700
"Jacob Mathew" <[EMAIL PROTECTED]> wrote:
> So far it all seems quite solid, but then there is the issue of URL's
> in javascript and other embedded content which can't identified by
> ProxyHTMLURLMap.
Yes it can. That's what ProxyHTMLExtended is for.
--
Nick
Thanks, I'll look into that. Though it still seems like I will have to
do this regular expression search for URL's which is what my main
issue is.
-Jacob
On Fri, May 30, 2008 at 8:23 AM, Jim Jagielski <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2008 at 08:17:22AM -0700, Jacob Mathew wrote:
>>
>>
On Fri, May 30, 2008 at 08:17:22AM -0700, Jacob Mathew wrote:
>
> So far it all seems quite solid, but then there is the issue of URL's
> in javascript and other embedded content which can't identified by
> ProxyHTMLURLMap. The solution proffered seem to be to use
> ProxyHTMLExtended and identify
I'm looking to setup apache as a reverse proxy to a couple of tomcat
servers. What I want is something like this:
www.proxy.com/app1 --->www.app1.target.com
www.proxy.com/app2 --->www.app2.target.com
>From what I can tell from the guides, to get this to work correctly
there needs to b
