HTTP encapsulated rsync??

[Aaron W Morris]

On 4/17/07, Robert Denton <robert at headsprout.com> wrote:
> 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

If some of the clients are already having to go through proxies, it
does complicate matters.  If that is the case, you may have to
investigate setting up said proxies to proxy again using proxy
chaining/cascading, but that's a bit out of scope for this mailing
list.

It's difficult for me to say what the problem is with the 503 error,
but it sounds like you're on the right track.

-- 
Aaron W Morris (decep)