Date: Thu, 27 Jun 2002 15:13:17 -0700 (PDT) From: Philip Hallstrom <philip@adhesivemedia.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: FTP/HTTP caching proxy for use with fetch and ports? Message-ID: <20020627151146.V31834-100000@cypress.adhesivemedia.com> In-Reply-To: <20020627173257.K37725-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
One problem I just realized with any caching proxy system is that it will treat the following as two separate files: http://somehost.com/specific-file.tgz http://some-other-host.com/specific-file.tgz even though I'd like it to treat them the same. This would come into play when certain servers are unreachable sometimes and not others (seems to happen with sourceforge to me a lot). Looks like NFS is probabably the easiest... thanks all! On Thu, 27 Jun 2002, Fernando Gleiser wrote: > On Thu, 27 Jun 2002, Philip Hallstrom wrote: > > > > > I started looking into caching proxies that would help automate this > > process somewhat, but I haven't had much luck. I tried jftpgw (FTP only) > > but could never get it to work right. Tried Apache's proxy which says it > > will do both, but it seemed to only cache HTTP and it's not really > > designed for "long term caching" so to speak. > > > > Anyone have any suggestions? Seems like this would be a common thing to > > reduce bandwidth... > > The most used caching proxy is squid. it does FTP and HTTP. It is in the > ports. > > But... For your particular problem, I'd export /usr/ports via NFS and > mount it on every host in your network. That way you download *and* compile > only once. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020627151146.V31834-100000>