httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10617] - SegFault in mod_ext_filter when content_type is null
Date Wed, 10 Jul 2002 01:23:37 GMT
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=10617>.
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=10617

SegFault in mod_ext_filter when content_type is null

trawick@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From trawick@apache.org  2002-07-10 01:23 -------
mod_ext_filter definitely needs to watch out for NULL content_type.
At the very least, the if statement should be changed to:

     if (ctx->filter->intype &&
         ctx->filter->intype != INTYPE_ALL &&
         (!f->r->content_type ||
          strcasecmp(ctx->filter->intype, f->r->content_type))) {

So if the user specifies a certain content_type to process we'll make
certain that there is a content_type associated with the response.
I do not know whether or not a NULL content_type always implies that there 
is no actual response body.  I doubt that it is true in general.  

mod_ext_filter should already handle an empty response okay (or that is another 
bug :) ), so the fix above should be sufficient for your problem and
we don't worry about whether or not there is a response body to filter.

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


Mime
View raw message