I went for a quick run of 'gdb bin/httpd' to see what happened in Rivet_SendContent and it seems to be working ok returning DECLINED upon a request for a cgi script. For what I know this is what Rivet is supposed to do. The request seems to be lost forever and apache even doesn't log it down. Only the error log has entries about timeout errors. Another thing that might be worth noticing is that quitting the debugging session gdb warns about a child process that has to be killed (never got that message debugging rivet/tcl requests). Therefore Apache could have got to the stage of forking the process for the cgi script, but for some reason the process is unable to produce any content (or headers).
I wonder if other functions (hooks) of Rivet could be confusing apache. In recent years other modules were the culprits of similar problems. Some googling shows that mod_sql_log (IIRC) was blocking the content generation of cgi-scripts and simply removing it restored the expected behavior.
I don't have much time these days, i have to put it off for a while. -- Massimo David Welton wrote:
Have you tried "eliminating" bits and pieces of mod_rivet (commenting them out or something) to see if you can figure out what exactly is causing the problem?
--------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
