Return-Path: Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org Received: (qmail 22307 invoked by uid 500); 28 Dec 2001 17:09:53 -0000 Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list cvs@httpd.apache.org Received: (qmail 22296 invoked by uid 500); 28 Dec 2001 17:09:53 -0000 Delivered-To: apmail-httpd-2.0-cvs@apache.org Date: 28 Dec 2001 17:09:52 -0000 Message-ID: <20011228170952.40148.qmail@icarus.apache.org> From: wrowe@apache.org To: httpd-2.0-cvs@apache.org Subject: cvs commit: httpd-2.0/modules/filters mod_include.c X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N wrowe 01/12/28 09:09:52 Modified: modules/filters mod_include.c Log: Another example, wherein our example in code/conf doesn't match our recommended practices Revision Changes Path 1.172 +2 -2 httpd-2.0/modules/filters/mod_include.c Index: mod_include.c =================================================================== RCS file: /home/cvs/httpd-2.0/modules/filters/mod_include.c,v retrieving revision 1.171 retrieving revision 1.172 diff -u -r1.171 -r1.172 --- mod_include.c 2001/12/26 12:07:55 1.171 +++ mod_include.c 2001/12/28 17:09:52 1.172 @@ -1079,7 +1079,7 @@ * The filename comparison catches a recursive include * with an ever-changing URL, eg. * + * "$REQUEST_URI/$QUERY_STRING?$QUERY_STRING/x" --> * which, although they would eventually be caught because * we have a limit on the length of files, etc., can * recurse for a while. @@ -3079,7 +3079,7 @@ * environment of the base document (for compatibility); that means * torquing our own last_modified date as well so that the * LAST_MODIFIED variable gets reset to the proper value if the - * nested document resets . + * nested document resets . */ r->subprocess_env = r->main->subprocess_env; apr_pool_join(r->main->pool, r->pool);