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, which I am anxious about doing in a high visibility website. I was looking to see if this was being done regularly and if I am being overly paranoid, or if my concern is valid. -Jacob On Fri, May 30, 2008 at 12:02 PM, Nick Kew <nick@xxxxxxxxxxxx> wrote: > On Fri, 30 May 2008 08:17:22 -0700 > "Jacob Mathew" <jacobgmathew@xxxxxxxxx> 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 Kew > > Application Development with Apache - the Apache Modules Book > http://www.apachetutor.org/ > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|