>Number: 4899 >Category: mod_perl >Synopsis: mod_perl causes status 204 codes to log as code 200 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Aug 24 11:10:06 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: FreeBSD 3.2-RELEASE, generic kernel. >Description: I have a script that accepts data via a GET, and returns a 'status 204, No response' (neat trick, BTW, for many situations). Before compiling in mod_perl, the log files (combined log) would properly report a code 204. Now, it reports in the log a code 200. The script IS correctly issuing a 204, it's just logging it incorrectly. I have 'PerlSendHeader On' and 'PerlHandler Apache::Registry' in my configuration files. >How-To-Repeat: Here's the url for the script, you can verify a code 204 is being issued:
http://192.215.16.145/cgi-bin/getscore.cgi >Fix: Nope. To be honest I feel a little silly reporting this as a bug, since it is so minor. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]
