Torsten Foertsch wrote:
If you look for something that follows your HTML more closely have a
look at mod_proxy_html (http://apache.webthing.com/mod_proxy_html/). It
can distinguish between
Ok, after a LOT of futzing around with other ideas and examples, I
tweaked another example off the web
On Thu 05 Feb 2009, André Warnier wrote:
> Mike Soultanian wrote:
> > André Warnier wrote:
> >> I mean, if in your browser you get such a response page, and look
> >> at the html source of the page, do you really see links to
> >> "http://myserver.tld:81/...";, or are they more like
> >
> > yup.. t
Mike Soultanian wrote:
André Warnier wrote:
I mean, if in your browser you get such a response page, and look at
the html source of the page, do you really see links to
"http://myserver.tld:81/...";, or are they more like
yup.. that's exactly what I'm getting :(
Well, if all the links a
André Warnier wrote:
I mean, if in your browser you get such a response page, and look at the
html source of the page, do you really see links to
"http://myserver.tld:81/...";, or are they more like
yup.. that's exactly what I'm getting :(
Mike Soultanian wrote:
Per my initial requirements, I was able to get reverse proxy working
pretty well so my legacy web app sees every request originating from
itself. To do this, I'm using the following:
proxyrequests off
NameVirtualHost *:80
NameVirtualHost myserver.tld:81
ProxyPass / h
Per my initial requirements, I was able to get reverse proxy working
pretty well so my legacy web app sees every request originating from
itself. To do this, I'm using the following:
proxyrequests off
NameVirtualHost *:80
NameVirtualHost myserver.tld:81
ProxyPass / http://myserver.tld:81/
P
