Received: (qmail 14170 invoked by uid 2012); 11 May 1999 12:59:28 -0000 Message-Id: <19990511125928.14169.qmail@hyperreal.org> Date: 11 May 1999 12:59:28 -0000 From: Robert Mitchell Reply-To: bmitchel@niac.usra.edu To: apbugs@hyperreal.org Subject: AddHandler causes error messages X-Send-Pr-Version: 3.2 >Number: 4384 >Category: config >Synopsis: AddHandler causes error messages >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue May 11 07:10:00 PDT 1999 >Last-Modified: Fri Aug 27 17:31:00 PDT 1999 >Originator: bmitchel@niac.usra.edu >Organization: >Release: 1.3.6-7 >Environment: Linux peaches.niac.usra.edu 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 i586 unknown RedHat 6.0 >Description: I am using RedHat 6.0 and Apache-1.3.6-7. I have added the following to my srm.conf: AddHandler eperl-parsed .ehtml Action eperl-parsed /cgi-bin/eperl When I access a .ehtml file from my browser eperl parses the page partially, but not completely. If I run it from the command line I can see that it creates an html page without errors, but my error_log contains the message: handler "eperl-parsed" not found for [file-name] It seems that a very simple .ehtml file will process correctly, but the message still appears in the error_log. A complex .ehtml will not display everything it is supposed to. >How-To-Repeat: http://niac.usra.edu/postdoc/t/etc/login.ehtml >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: fielding State-Changed-When: Fri Aug 27 17:30:59 PDT 1999 State-Changed-Why: The spurious warning message will be fixed in the next release. A patch can be found in PR 4807. The other problem sounds like an error in eperl's buffering, but you will have to ask the eperl author, or identify the problem in such a way that we can reproduce it locally. Ralf can probably find it given the script and enough info. .....Roy >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. ] [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! ]