From owner-freebsd-isp Tue Jul 24 8:47:59 2001 Delivered-To: freebsd-isp@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 50C6037B40C for ; Tue, 24 Jul 2001 08:47:53 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 15P481-0001T3-00; Tue, 24 Jul 2001 08:29:45 -0700 Date: Tue, 24 Jul 2001 08:29:43 -0700 (PDT) From: Tom Samplonius To: Jeremy Buckner Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Web Caching Engine In-Reply-To: <000701c11456$8e3893a0$1396f13f@caz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 24 Jul 2001, Jeremy Buckner wrote: > Has anyone ever used/configured FreeBSD as a web caching > engine. Can it be done or do I have to buy the $50,000 Cisco > product? Also it be seamless to my customers (no setting > proxy settings or anything like that). Any ideas? > Uhh... does Cisco make a cache? They make load balances, and content aware switches, but their cache product certainly isn't well known if it exists. If people are putting in dedicated caches, they go with NetApp NetCaches, or CacheFlow. You can do something similar in FreeBSD. You do transparent cache redirection, and Squid can do the caching. You will not get the request per second rates that a NetApp or CacheFlow can do, but if your site isn't large, no one will know the difference. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message