The following reply was made to PR general/2117; it has been noted by GNATS.
From: "David J. MacKenzie" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: general/2117: The CIDR syntax support for allow and deny finds the '/' in comments. Date: Wed, 22 Apr 1998 15:36:47 -0400 (EDT) On 22 Apr 1998 18:46:10 -0000, [EMAIL PROTECTED] said: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > Synopsis: The CIDR syntax support for allow and deny finds the '/' in > comments. > State-Changed-From-To: open-closed > State-Changed-By: dgaudet > State-Changed-When: Wed Apr 22 11:46:07 PDT 1998 > State-Changed-Why: > Comments aren't permitted on lines with directives; they must > be on their own line. It's always been that way. No idea what > your config does. That's fine, but in that case apache should print reasonable error messages rejecting lines with trailing comments, not do undefined things with them (such as silently accept them in some cases and suddenly break upon a new release :-). Checking correctness seems be the apache approach to configuration file processing in other respects.
