Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 76422 invoked by uid 500); 2 Apr 2001 20:14:55 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Delivered-To: moderator for tomcat-dev@jakarta.apache.org Received: (qmail 43652 invoked from network); 2 Apr 2001 16:16:58 -0000 Date: Mon, 02 Apr 2001 09:17:34 -0700 From: Bip Thelin Subject: Re: Behavior of new Server Side Include Functionality To: tomcat-dev@jakarta.apache.org Reply-to: bip@razorfish.com Message-id: <3AC8A61E.388654BA@razorfish.com> Organization: Razorfish MIME-version: 1.0 X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N "Craig R. McClanahan" wrote: > > > We can provide this option since this kind of makes sense in a web-app > > environment. However, I think the default way should be relative to the > > server's root following NCSA. What do you think? > > > > +1 on defaulting to NCSA rules, but I'd really like to see a configurable > option that virtual paths can be webapp-relative. Yes a webapp-relative option would seem good, but the option/standard way to run SSI should be NCSA compatible of course. You want to take this bug Amy? Let me know if you have any problems or need any help, I know I could of documented the code a bit better ;) ..bip