Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 11832 invoked from network); 16 Apr 2004 07:55:55 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Apr 2004 07:55:55 -0000 Received: (qmail 54060 invoked by uid 500); 16 Apr 2004 07:55:15 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 53949 invoked by uid 500); 16 Apr 2004 07:55:14 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 53933 invoked from network); 16 Apr 2004 07:55:14 -0000 Received: from unknown (HELO jupiter.hal-nine-zero-zero-zero.net) (217.160.171.50) by daedalus.apache.org with SMTP; 16 Apr 2004 07:55:14 -0000 Received: (qmail 23328 invoked from network); 16 Apr 2004 07:55:27 -0000 Received: from unknown (HELO news.perlig.de) (80.131.129.70) by jupiter.hal-nine-zero-zero-zero.net with SMTP; 16 Apr 2004 07:55:27 -0000 Date: Fri, 16 Apr 2004 09:55:25 +0200 From: =?ISO-8859-15?Q?Andr=E9?= Malo To: users@httpd.apache.org Message-Id: <20040416095525.36fc2977@parker> In-Reply-To: <407F43B4.2040205@finiteautomata.com> References: <407F43B4.2040205@finiteautomata.com> Organization: TIMTOWTDI X-Mailer: Yes! Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: Re: [users@httpd] 2.0.49 Server Side Includes X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N * "nick@finiteautomata.com" wrote: > I have been having some Server Side Includes issues with some of my > Virtual Hosts. I am running Apache/1.3.28 on RedHat Ent.3. We have had > issues where white space or blank lines cause Server Side Includes to > not work and we have to remove the blank space and blank lines > surrounding the Include statement. I was informed back in Feb. that it > was a bug in mod_include which would hopefully be fixed in 2.0.49. I > saw the CHANGES list for 2.0.49 and saw that "Fix mod_include's > expression parser to recognize strings correctly even if they start with > an escaped token" - Was this the fix? I wasn't sure so I compiled > 2.0.49 and converted all my sites over to 2.0.49 No, it's this one: *) Backport major overhaul of mod_include's filter parser from 2.1. The new parser code is expected to be more robust and should catch all of the edge cases that were not handled by the previous one. The 2.1 external API changes were hidden by a wrapper which is expected to keep the API backwards compatible. The change you've quoted was a minor edge case, where things like were not treated correctly. nd -- Winnetous Erbe: --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org