DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31759>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31759 ------- Additional Comments From [EMAIL PROTECTED] 2006-03-31 12:20 ------- Here's a patch to default handler to try: Index: server/core.c =================================================================== --- server/core.c (revision 386843) +++ server/core.c (working copy) @@ -3645,7 +3645,17 @@ e = apr_bucket_eos_create(c->bucket_alloc); APR_BRIGADE_INSERT_TAIL(bb, e); - return ap_pass_brigade(r->output_filters, bb); + status = ap_pass_brigade(r->output_filters, bb); + if (status == APR_SUCCESS + || c->aborted) { /* broken I/O isn't an HTTP issue, so no + * error status applies + */ + return OK; + } + else { + /* no way to know what type of error occurred */ + return HTTP_INTERNAL_SERVER_ERROR; + } } else { /* unusual method (not GET or POST) */ if (r->method_number == M_INVALID) { >What do we need to do to get developers to stop playing >with grand new features that aren't crucial to basic >operation, and fix the core? what can you do to help? * please refrain from complaining or otherwise expressing frustration via the PR database... that sends a signal to those who volunteer their time that their effort is inadequate... while that may be true for your problem, overall there are many problems diagnosed and solved via the PR database, and there is no benefit from airing your grievance... * continue to submit problem reports... every one is looked at even if there doesn't appear to be any activity on it... * help us out as much as possible with your report... this includes providing relevant documentation when you create the report as well as trying to respond quickly to questions we ask or suggestions we make... if you aren't willing to help us work on your issue, why are we wasting our time in the first place? * use the source... you have access to the source code... you (or someone you know or can hire with the proper skills) have the opportunity to find the code that is causing you a problem and fix it, even if the fix is particular to your environment and not suitable for general distribution * if your company depends on Apache httpd, consider sponsoring a skilled developer to get involved in the maintenance and ongoing development of Apache httpd * consider paying for support from one of the companies that sells support for Apache httpd (or servers based on Apache httpd) and contributes to the open source development effort of Apache httpd -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
