Received: (qmail 19731 invoked by uid 2012); 21 Nov 1998 08:24:27 -0000
Message-Id: <19981121082427.19730.qmail@hyperreal.org>
Date: 21 Nov 1998 08:24:27 -0000
From: Scott Anguish <newsletters@digifix.com>
Reply-To: newsletters@digifix.com
To: apbugs@hyperreal.org
Subject: Continuous handler XXXX not found messages
X-Send-Pr-Version: 3.2

>Number:         3436
>Category:       general
>Synopsis:       Continuous handler XXXX not found messages
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Nov 21 00:30:01 PST 1998
>Last-Modified:  Fri Aug 27 17:24:50 PDT 1999
>Originator:     newsletters@digifix.com
>Organization:
>Release:        1.3.3
>Environment:
OpenStep 4.2 - Intel - cc
>Description:
I have declared a new type for files of extension .list
they are to be executed by /cgi-bin/sub_include

My usage is largely as follows within an HTML document
<!--#include virtual="/articles_links/template.list" --> <BR>

In srm.conf, I make the following declaration

AddHandler sub_includes-parse .list
Action sub_includes-parse /cgi-bin/sub_includes


This works without any complaint or error on 1.2.6.  However on 1.3.3 I get complaints of

handler "sub_include-parse" not found

for each file that has one of these includes.

It does execute /cgi-bin/sub_includes, but only includes some of the data that should be output, and then spews that error to the error log.

Returning to 1.2.6 fixes this problem



>How-To-Repeat:

>Fix:

>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: fielding
State-Changed-When: Fri Aug 27 17:24:49 PDT 1999
State-Changed-Why:

The spurious warning message will be fixed in the next release.
A patch can be found in PR 4807.

.....Roy

>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]