httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8037] New: - documentation of Script directive does not define arguments well enough
Date Fri, 12 Apr 2002 21:02:27 GMT
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=8037>.
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=8037

documentation of Script directive does not define arguments well enough

           Summary: documentation of Script directive does not define
                    arguments well enough
           Product: Apache httpd-1.3
           Version: 1.3.23
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Documentation
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: bugapache@bitdance.com


I've been fighting with trying to get PUT scripts working on my
server off and on for six months, searching the web for examples
and following them without success.  It turns out that the
problem was that I was using the file system path name for the
cgi argument of the 'script PUT' directive instead of the URL.
The script ran, but an error message was generated that said
that the full filesystem path name, with the location of the
PUT file appended, did not have permission for a PUT request.
Needless to say, this totally confused me and lead to six months
of a non functioning site.

Hmm.  Although I'm submitting this as a doc bug (script should
be explicit about what it is expecting for the 'cgi-script'
argument), the actual bug may more properly be a bug in the
error message that results from putting the wrong thing
for that argument...

Mime
View raw message