This is an interesting idea. Here is what I am trying:
I have set up squid to listen on port 81, since rsync on the same
machine is already listening for requests on 80. I have set the
RSYNC_PROXY env var to the hostname:81 and rand a quick test. The
result is that I am getting this error:
bad response from proxy -- HTTP/1.0 503 Service Unavailable
rsync: failed to connect to 192.168.233.56: Success (0)
I am thinking this is a problem with the squid config not passing the
rsync request to the rsync daemon.
Another though occurs to me: many of the clients are behind enforced
proxies of their own, set via an env var: http_proxy. Is this going
to work with the RSYNC_PROXY? Since the rsync proxy is pointing to an
http port on a server, will the request automatically be channeled
through the enforced http_proxy?
Robert
On Apr 17, 2007, at 4:00 PM, Aaron W Morris wrote:
On 4/17/07, Robert Denton <[EMAIL PROTECTED]> wrote:
Do you mean for example.. Instead of running rsync on port 80, have
rsync listen for requests on 873 as usual, but also have squid
running on the same server listening for port 80 connections, and
then just configure squid to send all port 80 traffic to 873?
Robert
I was thinking more along the lines of creating a proxy for all of
your rsync requests.
You would not necessarily have to do any special configuration to
squid (except allow CONNECT with port 873, something I know has to be
done with mod_proxy), it should route the request itself. Apache with
mod_proxy would work as well.
--
Aaron W Morris (decep)
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
