AW: AW: [squid-users] reverse-proxy for multiple domains
i guess i mixed something up or my english is not as good as it shut be. i
read this manual [url]http://squid.visolve.com/white_papers/reverseproxy.htm#ee[/url]
and thought: "this is what you need."
we got two webservers an differnet ports and of course different ip's.
i wannted to put a reverse-proxyx in front of them to cache some requests
but i think this is nor what i mentionted in the postings so far?
> -----Ursprungliche Nachricht-----
> Von: Henrik Nordstrom [mailto:firstname.lastname@example.org]
> Gesendet: Donnerstag, 26. Februar 2004 13:57
> An: [email]email@example.com[/email]
> Cc: [email]firstname.lastname@example.org[/email]; [email]email@example.com[/email]
> Betreff: Re: AW: [squid-users] reverse-proxy for multiple domains
> On Thu, 26 Feb 2004 [email]firstname.lastname@example.org[/email] wrote:
> > Why httpd_accel_port 0?
> > cause i read it somewhere i don't remember anymore. i[/color]
> thought the port must[color=green]
> > be zero in connection with the virtual httpd_accel_host.[/color]
> Enabling httpd_accel_port virtual mode enables port-based
> virtual hosts.
> > do i have to change it to the port of the web-server?[/color]
> This is required.
> These directives control how Squid reconstructs the complete
> requested URL
> on accelerated requests
> httpd_accel_uses_host_header tells Squid to use the Host
> header of the
> request if available.
> httpd_accel_host tells what host name to use if
> httpd_accel_uses_host_header is not enabled or if the request
> does not
> have a Host header.
> httpd_accel_port tells what port to use in the reconstructed
> url. If 0
> then the port number of the http_port will be used.
> So if you have
> http_accel_host virtual
> http_accel_port 0
> http_accel_uses_host_header off (or request without Host header)
> http_port 220.127.116.11:8888
> then the URL as seen by Squid will become
> and this is the URL Squid will try to retreive, which most
> likely is not
> what you want unless you are using a redirector to fix up
> this URL into
> something which makes sense.
> The recommended accelerator setup for Squid-2.5 is
> # Host to assume if there is no Host header
> httpd_accel_host your.main.domain.name
> # Normal web port
> httpd_accel_port 80
> # Domain based virtual host support
> httpd_accel_uses_host_header on
> # Required for RFC compliance
> httpd_accel_with_proxy on
> Then add the accelerated hostnames to /etc/hosts with the
> addresses of the
> real web servers, and configure Squid access controls to
> limit what may be
> # Base ACLs
> acl all src 0.0.0.0/0
> acl port80 port 80
> acl http proto http
> # Give access only to our accelerated servers
> acl ourwebsites dstdomain accelerated.web.name
> http_access allow http port80 ourwebsites
> # Deny all other uses
> http_access deny all
> For Squid-3 the setup is a little different, but Squid-3.0 is not yet
> released so more on that later.