On mån, 2007-10-01 at 15:55 +0200, Sylvain Viart wrote: > Now with url_rewrite_program, http_port accel, cache_peer it seems I > should be able to do it in full squid.conf directive. Yes, as long as you don't need to actually rewrite the URL, just have it forwarded to the properserver. > For now my squid works on the load balancing side, but not on filtering, > as the filtered url are also balanced on the originserver. > > Here is my related squid.conf directives: > > # I do vhost namebased > http_port 80 defaultsite=my.site.com vhost > > # the rewrite filter > url_rewrite_program /etc/squid/redirector.pl > url_rewrite_children 5 > url_rewrite_concurrency 0 > url_rewrite_host_header off > > cache_peer php-01 parent 80 0 no-query originserver round-robin weight=1 > login=PASS > cache_peer php-02 parent 80 0 no-query originserver round-robin weight=1 > login=PASS > > /etc/squid/redirector.pl return, the incomming URL if not matched, or > the url with the domain replaced with the filer's hostname if it matches > a static document. > ex: http://filer/imagepath/someimg.jpg > > I don't find any good doc on how to use all those rewriting url + peer > balancing etc. Can someone point me to some good ref? If you can drop the url rewriter and use cache_peer_access instead to direct which requests is acceptable to send to which peer. Regards Henrik
Attachment:
signature.asc
Description: This is a digitally signed message part
