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 15113] New: - Child Segmentation Fault when Mod_Cache receive a 302 ok response
Date Thu, 05 Dec 2002 16:30:41 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=15113>.
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=15113

Child Segmentation Fault when Mod_Cache receive a 302 ok response

           Summary: Child Segmentation Fault when Mod_Cache receive a 302 ok
                    response
           Product: Apache httpd-2.0
           Version: 2.0.43
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Major
          Priority: Other
         Component: mod_cache
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: tcastelle@generali.fr


Hello there !

We have this friendly message :

"[notice] child pid 19283 exit signal Segmentation fault (11)"

when we try to retrieve some web pages through an Apache 2.0.43 proxy running
mod_cache, from a serveur returning 302 ok responses.

I looked a little bit in the code, and, I'm not a specialist, but the problem
seems to be in mod_cache.c, in the cache_in_filter function, when there is a
call to apr_pstrcat :

if (r->status != HTTP_OK && r->status != HTTP_NON_AUTHORITATIVE
         && r->status != HTTP_MULTIPLE_CHOICES
         && r->status != HTTP_MOVED_PERMANENTLY
         && r->status != HTTP_NOT_MODIFIED) {
         /* RFC2616 13.4 we are allowed to cache 200, 203, 206, 300, 301 or 410
          * We don't cache 206, because we don't (yet) cache partial responses.
          * We include 304 Not Modified here too as this is the origin server
          * telling us to serve the cached copy.
         */
         reason = apr_pstrcat(p, "Response status %d", r->status);
}

Commenting this line prevent us from having this problem (on this particular
web-serveur) but I don't think it's really clean... ;-)

Can you look at this ?

Thanks in advance,

Thomas.

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


Mime
View raw message