Received: (qmail 8249 invoked by uid 2012); 18 Feb 1999 18:19:35 -0000 Message-Id: <19990218181935.8248.qmail@hyperreal.org> Date: 18 Feb 1999 18:19:35 -0000 From: John Ray Reply-To: jray@postoffice.ag.ohio-state.edu To: apbugs@hyperreal.org Subject: CGIs that require ANY sort of processing time fail. No errors are logged. X-Send-Pr-Version: 3.2 >Number: 3918 >Category: mod_cgi >Synopsis: CGIs that require ANY sort of processing time fail. No errors are logged. >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: feedback >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Feb 18 10:20:01 PST 1999 >Last-Modified: Thu Mar 25 12:20:01 PST 1999 >Originator: jray@postoffice.ag.ohio-state.edu >Organization: >Release: 1.3.4 >Environment: OpenStep 4.0, NeXT Computer, Inc. version cc-475, gcc version 2.5.8 >Description: I've compiled a plain-jane Apache 1.3.4, and have configured it as appropriately as possible. This was to be an upgrade from v1.2. Unfortunately, any CGI that takes awhile to generate its output has stopped working. I'm assuming this has something to do w/ the new non-buffered CGI processing. What it *looks* like is that the server doesn't recieve any data from the CGI within a certain timeout period, and simply says "thats it", and kills the CGI. There is nothing logged to the error log file (which is set on debug) and the browser displays whatever data it has managed to get. CGIs which run *quickly* work just fine! >How-To-Repeat: Here's our 1.2 server: http://www.ag.ohio-state.edu/~majordom/showmajor.cgi This is 1.3.4: http://www.ag.ohio-state.edu:8080/~majordom/showmajor.cgi The problem should be obvious upon looking at the two URLs. >Fix: Well, with nothing showing up in the error log, I have no idea what's going wrong :( >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Thu Mar 25 12:06:21 PST 1999 State-Changed-Why: When you say the script takes a while to generate output, are you including the emission of the CGI response header in that? The server needs to hear that reasonably quickly; the actual content body can take longer without any problem. Severity-Changed-From-To: critical-serious Severity-Changed-By: coar Severity-Changed-When: Thu Mar 25 12:06:21 PST 1999 Category-Changed-From-To: general-mod_cgi Category-Changed-By: coar Category-Changed-When: Thu Mar 25 12:06:21 PST 1999 From: John Ray To: coar@apache.org Cc: apbugs@apache.org Subject: Re: mod_cgi/3918: CGIs that require ANY sort of processing time fail. No errors are logged. Date: Thu, 25 Mar 1999 15:19:00 -0500 > When you say the script takes a while to generate output, > are you including the emission of the CGI response header > in that? The server needs to hear that reasonably quickly; > the actual content body can take longer without any > problem. > Nope, its something other than that... for example, look at this URL: Apache 1.2: http://www.ag.ohio-state.edu/~jray/quicktest.cgi Apache 1.3.4: http://www.ag.ohio-state.edu:8080/~jray/quicktest.cgi The source for quicktest.cgi is nothing but: #!/usr/bin/perl $|=1; print "Content-type: text/html\n\n"; print "Start.

"; sleep 1; print "Finish!"; With 1.2, it executes as you'd expect (for a buffered CGI)... With 1.3.4, you immediately get the "Start" - then it just dies. :( --- John >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]