DO NOT REPLY [Bug 30033] - mod_isapi: WriteClient not able to write HTTP-Headers

[bu...@apache.org]

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





------- Additional Comments From matt@iamcode.net  2006-05-31 05:55 -------
Created an attachment (id=18374)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18374&action=view)
Patch to not clobber the ISAPI's response code.

I've attached a patch to 2.2.2's mod_isapi.c which should correct this
behavior. I've run it against a suite of ISAPI extensions, all of which give
their correct responses as far as I can tell.

What seems to be the issue is that ap_scan_script_header_err_strs likes to
return 0 (or some other value which is not the HTTP status). The current
mod_isapi sticks this result in as the HTTP status. Needless to say, this is
quite unexpected. Since mod_isapi's send_response_header already gets the
correct value, there's no reason that I can see to second-guess it.

If someone can review this trivial patch for sanity, I'd appreciate it. I can't
find any breakage, but I assume that someone did that for a reason.

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org