[satang]

When you said "no header at all", do you mean that there is only a leading empty line to indicate the end of response header? or only the response status line followed by the empty line? I think Apache should add necessory header to the response to make it comply with HTTP protocol. Would you mind capturing an example response with "lynx -mime_header" and post it here?

No header at all! I used `tcpflow' to capture the output and discovered this (tcpflow really is the bomb for debugging problems like this :-)). Yes, Apache should be making sure it is complying with the HTTP protocol, given that it is (supposedly) an HTTP server, not just a remote buffer overflow exploit server. This made me doubt the former claim.

Normally, with CGI output, without "non-parsed headers", any script response without a header has a default header added, as do headers without the "HTTP/x.y nnn ..." code. So, if you take a working CGI script:

#!perl
use CGI;
print "Hello, world!\n";

And run it under mod_perl, Apache never sends a header, unless you add:

#!perl
use CGI;
my $cgi = new CGI;
print $cgi->header, "Hello, world!\n";

In this case, the CGI.pm module detects it is running under mod_perl and appropriate hacks^H^H^H behaviour happens (the same as $cgi->header(-nph => 1)). HTTP/0.9 worked like this IIRC, so maybe web browsers tolerate the RFC violation.

In this case, I fixed the code that was missing the explicit header printout.

Whether to ignore the missing header, is a design decision - however the lack of eventual timeout would be nice to have fixed.

Hey I've almost got enough virtual hosts on my LSWS to put forward the case to buy a licence soon! :wink: