From: Jeff Trawick [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 5:50 PM
Thanks for confirmation. At least I know I'm not barking
up the wrong tree.
We can't close the socket. Otherwise, how would we read the
output of
the CGI back in the child process [thread] that sends
So use mod_cgi :)
(If there isn't a compelling performance difference, that makes sense
from Apache's perspective because mod_cgid is unfortunately
complicated
and it isn't worth more tricks if there's no sense in using it in the
first place.)
My understanding of the world is that mod_cgid is
Jeff Trawick wrote:
If somebody doesn't care about local security, mod_cgid should be able
to see something like
scriptsock 127.0.0.1:
in the config file and use a TCP socket instead of Unix socket for
communication with the daemon.
Alternatively the handler could store the request body in a
I'm running into a problem with some code based on the
mod_cgid module, on hp-ux. I've also submitted
the underlying problem to comp.systems.hp.hpux.
The problem is that the underlying cgi hangs on a read
from stdin when there is actually no data left to be read.
I can reduce this to a simple
