From owner-freebsd-isp Thu Sep 3 07:22:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22354 for freebsd-isp-outgoing; Thu, 3 Sep 1998 07:22:23 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22349 for ; Thu, 3 Sep 1998 07:22:21 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id KAA17947; Thu, 3 Sep 1998 10:20:43 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Graeme Tait cc: isp@FreeBSD.ORG, info@boatbooks.com From: "Gary Palmer" Subject: Re: Anyone running FrontPage with Apache on stable/current? In-reply-to: Your message of "Thu, 03 Sep 1998 04:33:45 PDT." <35EE7E99.298E@webcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Sep 1998 10:20:43 -0400 Message-ID: <17943.904832443@gjp.erols.com> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Graeme Tait wrote in message ID <35EE7E99.298E@webcom.com>: > I have never understood why this needs to be (that the content is not > cacheable). For content that is quasi-static, why could not the ASP pages > be served so as to be cacheable? Because ASP pages can make decisions on what to return depending on browser-specific or IP specific information? I have never seen ASP, but if its similar to Apache's SHTML, then that would be a problem ... caches *cannot* cache browser-specific content and then return it to all browsers hitting that cache. That would return incorrect content and the pages wouldn't display properly. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message