My guess is the following:As is works for the first backend, this shows that Server/Browser *can* 'remember' where to send a relative path to -- I guess by response parameters. So, although two hrefs in *.html files of two different backends a.net, b.net may be identical -- say 'page.html', the browser will glue it
a.net ++ / ++ page.html -> a.net/page.html b.net ++ / ++ page.html -> b.net/page.htmlTo my impression, mod_proxy_html & mod_substitute replace the *relative href path* part, i.e.,
a.net ++ / ++ wiki/page.html as explained, this is problematic.What I am rather looking for is a substitution of the *response parameter path*, i.e.,
a.net/wiki ++ / ++ page.html As this appears much simpler, I guess it might exist. Any ideas? Thanks a lot, again, Nick On 02/12/2011 06:10 AM, Devraj Mukherjee wrote:
On Sat, Feb 12, 2011 at 1:57 PM, Nick Kew<nick@xxxxxxxxxxxx> wrote:On Fri, 11 Feb 2011 22:52:25 +0100 Nick Rudnick<joerg.rudnick@xxxxxxxxxxx> wrote:I run into problems with the second backend, as its relative paths lack the wiki/ prefix.http://www.apachetutor.org/admin/reverseproxiesThat article uses mod_proxy_html to rewrite URLs in the page body. I have a similar setup and now use mod_substitute to do the same thing. Much simpler and don't have to build the module separately (not that its difficult). Upgrades are easier. I prefer modules distributed as part of the Apache core. --------------------------------------------------------------------- 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