www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter <pe...@helpnet.com.au>
Subject Re: os-windows/7593: Space in filename bombs Apache
Date Fri, 20 Apr 2001 06:00:02 GMT
The following reply was made to PR os-windows/7593; it has been noted by GNATS.

From: Peter <peter@helpnet.com.au>
To: wrowe@apache.org
Cc: apbugs@Apache.Org
Subject: Re: os-windows/7593: Space in filename bombs Apache
Date: Fri, 20 Apr 2001 15:57:19 +1000

 Fair enough. Forget the suggestion for the bypass.
 At least have Apache produce an error message instead of bombing. The
 crash soaked up quite some time finding the exact cause of the error.
 There were no messages in any of the logs. I had changed a lot of lines
 in both .conf and php.ini while installing PHP and adding the extra web
 site to use PHP. Testing them by trial and error was time consuming.
 For a while I thought it was PHP and ISAPI.
 If Apache had put out a message indicating what it was attempting when
 the crash happened, I could have gone straight to the offending line in
 .conf and fixed it.
 wrowe@apache.org wrote:
 > [In order for any reply to be added to the PR database, you need]
 > [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 > [subject line starts with the report component and number, with ]
 > [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 > ["Re: general/1098:").  If the subject doesn't match this       ]
 > [pattern, your message will be misfiled and ignored.  The       ]
 > ["apbugs" address is not added to the Cc line of messages from  ]
 > [the database automatically because of the potential for mail   ]
 > [loops.  If you do not include this Cc, your reply may be ig-   ]
 > [nored unless you are responding to an explicit request from a  ]
 > [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 > Synopsis: Space in filename bombs Apache
 > State-Changed-From-To: open-closed
 > State-Changed-By: wrowe
 > State-Changed-When: Thu Apr 19 22:07:40 PDT 2001
 > State-Changed-Why:
 > Thank you for the suggested path to resolve your config
 > error.
 > However, many directives in Apache take a variable number
 > of arguments.  It would be very misleading to allow those
 > to accept unquoted file names.  As with unix, any pathname
 > that contains a space character must be quoted.  This is
 > true even with the command shell dir command.
 > For the sake of consistency, spaces are required in every
 > config directive for path names containing spaces.
 > Class-Changed-From-To: sw-bug-mistaken
 > Class-Changed-By: wrowe
 > Class-Changed-When: Thu Apr 19 22:07:40 PDT 2001

View raw message