[In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> 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: parsing apears to stop at the CGI file. State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Wed May 26 08:03:09 PDT 1999 State-Changed-Why: Yes, this is working as designed. What you are doing is passing the name of a file to the script through the path-info mechanism. Nothing requires the path-info URI component to be a filename, or any other particular type of information, so Apache treats it as an opaque string rather than trying to assume it knows what it is and wasting possibly erroneous effort on it. If the path-info were arbitrary data, such as "MontyPython", Apache would spend cycles and disk I/O trying to treat it as a filename. And what if the arbitrary data just *happened* to match the name of a file outside the server's mapping space? What if MontyPython actually *was* the name of a file, but wasn't intended that way in the URI? So Apache doesn't make assumptions like this. Sorry.. Class-Changed-From-To: sw-bug-support Class-Changed-By: coar Class-Changed-When: Wed May 26 08:03:09 PDT 1999
