Received: (qmail 20471 invoked by uid 2012); 10 Jul 1998 15:42:06 -0000 Message-Id: <19980710154206.20470.qmail@hyperreal.org> Date: 10 Jul 1998 15:42:06 -0000 From: Michael Parker Reply-To: parker@austx.tandem.com To: apbugs@hyperreal.org Subject: Seeing alot of these: "handler "cgi-wrapper" not found for" since upgrading X-Send-Pr-Version: 3.2 >Number: 2584 >Category: mod_actions >Synopsis: Seeing alot of these: "handler "cgi-wrapper" not found for" since upgrading >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Jul 10 08:50:01 PDT 1998 >Last-Modified: Fri Aug 27 17:38:28 PDT 1999 >Originator: parker@austx.tandem.com >Organization: >Release: apache_19980709130029 >Environment: SunOS sauron 5.5.1 Generic_103640-05 sun4u sparc SUNW,Ultra-2 Server Version: Apache/1.3.1-dev (Unix) mod_perl/1.12_01-dev gcc version 2.7.2.1 >Description: I'm not really sure whats going on here. I recently upgraded to 1.3.1-dev and started getting these in the error log: [warn] handler "cgi-wrapper" not found for I have this in my httpd.conf file: # To use cgiwrap for CGI scripts: AddHandler cgi-wrapper .cgw Action cgi-wrapper /cgi-bin/cgiwrap2/ The script runs seemingly without problems. I looked through the changes and noticed a reference to PR#2529 which seems to have introduced this error message. I'm thinking that the message is bogus since the handler seems to actually be being called. >How-To-Repeat: See above >Fix: >Audit-Trail: State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Fri Jul 10 09:44:31 PDT 1998 State-Changed-Why: Can your reproduce them on any access to a .cgw script, or is it just certain ones? Can your reproduce them yourself at all or are they just in the logs? I can't reproduce it myself, so perhaps there is some other condition necessary? Can you try on a test server without any extra modules (eg. no mod_perl) compiled in? From: Marc Slemko To: Apache bugs database Cc: Subject: Re: mod_actions/2584: Seeing alot of these: "handler "cgi-wrapper" not found for" since upgrading (fwd) Date: Fri, 10 Jul 1998 10:36:01 -0700 (PDT) ---------- Forwarded message ---------- Date: Fri, 10 Jul 1998 12:02:52 -0500 From: Michael Parker To: marc@hyperreal.org, apache-bugdb@apache.org Subject: Re: mod_actions/2584: Seeing alot of these: "handler "cgi-wrapper" not found for" since upgrading It happens for any of the .cgw scripts that I run. I'll compile a server this afternoon without mod_perl and see how it reacts. Michael On Fri, Jul 10, 1998 at 04:44:32PM -0000, marc@hyperreal.org wrote: > Synopsis: Seeing alot of these: "handler "cgi-wrapper" not found for" since upgrading > > State-Changed-From-To: open-analyzed > State-Changed-By: marc > State-Changed-When: Fri Jul 10 09:44:31 PDT 1998 > State-Changed-Why: > Can your reproduce them on any access to a .cgw script, or is > it just certain ones? Can your reproduce them yourself > at all or are they just in the logs? > > I can't reproduce it myself, so perhaps there is some other > condition necessary? Can you try on a test server > without any extra modules (eg. no mod_perl) compiled in? State-Changed-From-To: analyzed-feedback State-Changed-By: coar State-Changed-When: Thu Apr 29 07:20:53 PDT 1999 State-Changed-Why: [This is a standard response.] This Apache problem report has not been updated recently. Please reply to this message if you have any additional information about this issue, or if you have answers to any questions that have been posed to you. If there are no outstanding questions, please consider this a request to try to reproduce the problem with the latest software release, if one has been made since last contact. If we don't hear from you, this report will be closed. If you have information to add, BE SURE to reply to this message and include the apbugs@Apache.Org address so it will be attached to the problem report! State-Changed-From-To: feedback-closed State-Changed-By: fielding State-Changed-When: Fri Aug 27 17:38:27 PDT 1999 State-Changed-Why: The spurious warning message has been fixed post-1.3.9. See PR 4807. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]