Re: Handling the 'User pressed Stop button' case - not working

they get impatient. If they hit STOP I really want to know about it so I can free up CPU resources for when they hit RELOAD to try agin. Any helpful hints would be most appreciated. -- Matthew Darwin Community Volunteer [EMAIL PROTECTED] http://www.davin.ottawa.on.ca/~matthew/

Handling the 'User pressed Stop button' case - not working

uest. Is the first Apache not closing the socket for the second Apache? Has anybody run into this before? I'm using Linux 2.2 with Apache/1.3.19 (Unix) mod_perl/1.25 Configuration details available upon request. -- Matthew Darwin Community Volunteer [EMAIL PROTECTED] http://www.davin.ottawa.on.ca/~matthew/

sending a response without a Content-Type header

content); } This is actually what the device returns: % telnet realdevice 80 Trying 1.2.3.4... Connected to realdevice. Escape character is '^]'. GET / HTTP/1.0 200 OK [chop] -- Matthew Darwin [EMAIL PROTECTED]

segfault: perl 5.6.0, apache 1.3.12, mod_perl 1.24 and XML::Parser

My apache dies about 30% of the time when handling any mod_perl request that requires XML::Parser. Any other page (even pages that use mod_perl) are 100% ok. Are there any known issues with this (besides the requirement for --disable-rule=expat)? This all worked fine with perl 5.005_03 + mod_p