Kind of an odd one, we just upgraded a major application from Mod_perl 1.29 running on Apache 1.3.34 (compiled from source) to modperl 2.0.2/apache 2.2.3 (default Centos RPMs, not from source)
Occasionally ParseHeaders misses detecting the "Content-Type: text/html" header (it gets printed in the content instead) causing a rendering problem as Apache defaults to text/plain. Whenever this happens we get odd garbage in the logs: [Thu Sep 20 21:34:24 2007] [error] [client 172.31.18.13] malformed header from script. Bad header= <order>German Duden</order>: userInfo.pl, referer: http://ncdcwebn3b.ncdc.ncus/cgi-bin/ [Thu Sep 20 21:58:30 2007] [error] [client 192.168.18.13] malformed header from script. Bad header=\xebP\x82b\xb83\xc1\x81\xb7\x88\xe9tP\x95Y\x19\xb1\xa8\xf0\rSG\x14\x91\x88\x18\x9c#\xde\x8c: testscript.pl, referer: http://localhost.localdomain/cgi-bin/ [Fri Sep 21 14:58:37 2007] [error] [client 192.168.18.13] malformed header from script. Bad header=Italian</order>: testscript.pl, referer: http://localhost.localdomain/cgi-bin/ Searching my harddrive, those strings appear in the mysql driver but we've seen chunks of the gpl, and other weird random data in those errors. It almost looks like a wild pointer. Our config looks like this: <FilesMatch "\.pl$"> SetHandler perl-script PerlHandler ModPerl::PerlRun PerlOptions +ParseHeaders Options +ExecCGI </FilesMatch> The scripts are fairly complicated, and we have no success on replicating this outside of our environment. Anyone have any ideas?