Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
Date: 7 May 2003 01:22:11 -0000
Message-ID: <20030507012211.25240.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 19688]  -
    ap_fputs, ap_fputc,
 ap_fwrite pass wrong filter pointer to ap_filter_flush?

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=19688>.
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=19688

ap_fputs, ap_fputc, ap_fwrite pass wrong filter pointer to ap_filter_flush?


------- Additional Comments From MMADKI@Doorways.org  2003-05-07 01:22 -------
I went back to Ryan Bloom's 09/2001 article on writing output filters 
(http://www.onlamp.com/pub/a/apache/2001/09/13/apache_2.html) and it states 
very clearly that the filter argument to all of these routines is filter-
>next.  I had read this article, but apparently not with enough attention to 
detail.  Then I went to the documentation line I quoted above in the source and 
confused myself.

Sorry for registering a bug on this.  I still believe the doc should be fixed 
and it is in fact taken from the code (as it should be).  I'm willing to do it 
myself and submit diffs if requested.

Mea culpa, mea culpa, mea culpa.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org