Ime Smits <[EMAIL PROTECTED]> wrote:
>
>Now this all works fine except when a client side redirect using meta
>http-equiv tags occurs, in which case the hostname part in the url holds a
>:81 suffix, effectively bypassing the proxy.
Use the following config:
Listen 81
Port 80
In
I was going to suggest having the backend server listen on localhost:80,
with the proxying server listening on :80, then the
redirects from either would be to port 80.
This suggestion of Tony's certainly seems like a cleaner solution though.
(Plus, I learned something I didn't know about this in
| Use the following config:
| Listen 81
| Port 80
| In the presence of a Listen directive, the Port directive acts like
| ServerName, i.e. it's what the server calls itself regardless of the
| name that other people use to get to it.
OK, thanks a lot, that does the trick. I tried that earlier tod
For what it is worth, I once again fixed my own problem by hacking
http_core.c on the backend:
[root@nobel src]# diff -U 6 ../build/apache_1.3.14/src/main/http_core.c
http_core_hack-1.3.14.c
--- ../build/apache_1.3.14/src/main/http_core.c Tue Oct 10 19:33:09 2000
+++ http_core_hack-1.3.14.c M
On Mon, 12 Feb 2001, Ime Smits wrote:
> Hi,
>
> I have a mod_perl backend listening on *:81 and a proxy in front of it
> listening on *:80, both using mod_vhost_alias configured with
>
I'm using squid in httpd-accellerator mode on port 80.
And I have no problems with redirects and with any
Hi,
I have a mod_perl backend listening on *:81 and a proxy in front of it
listening on *:80, both using mod_vhost_alias configured with
VirtualDocumentRoot /www/site/%0
i.e. www.mydomain.com will have /www/site/www.mydomain.com as it's document
root. The frontend has
RewriteEngine On
