DO NOT REPLY [Bug 8311] New: - error in PUT directive gives confusing error messages

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8311>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8311

error in PUT directive gives confusing error messages

           Summary: error in PUT directive gives confusing error messages
           Product: Apache httpd-1.3
           Version: 1.3.24
          Platform: All
        OS/Version: FreeBSD
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: bugapache@bitdance.com


Misunderstanding the examples of setting up PUT, I coded the 
following directive in a directory section on a virthost:

  Script PUT /var/www/virthost/somesite/put.pl

This did not work.  When attempting to access it, however, I got an
error message that I did not have permission to use the PUT
directive on /var/www/virthost/somesite/put.pl/dir/putfile.
The error log showed 'Invalid URI in request PUT /dir/putfile'.
Neither of these error messages made it clear to me that the
issue was that PUT was expecting a URI, while I had coded a
file system path.  In general in Apache I thought that one
referred to scripts via filesystem paths and *not* URLs, for
security reasons.

IMO, there must be a way for the script PUT to recognize that its
argument is not a valid script, and report *that* in the
error message.