The following reply was made to PR os-solaris/3298; it has been noted by GNATS.
From: "Greg Haygood" <[EMAIL PROTECTED]> To: "'Marc Slemko'" <[EMAIL PROTECTED]> Cc: "'Apache bugs database'" <[EMAIL PROTECTED]> Subject: RE: os-solaris/3298: bad CGI headers due to /etc/resolv.conf Date: Tue, 27 Oct 1998 12:48:00 -0500 ah, it appears to be a sendmail issue. rather obscure, but oh, well. thanks for the help, -g -----Original Message----- From: Marc Slemko [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 27, 1998 12:24 PM To: Greg Haygood Cc: Apache bugs database Subject: RE: os-solaris/3298: bad CGI headers due to /etc/resolv.conf On Tue, 27 Oct 1998, Greg Haygood wrote: > > i have, and it works fine. also, i changed the script with > > print "content-type: text/plain\n\n" > $|++; > > at the start of the script, and > > print "bye"; > exit(0); > > at the end of the perl script, and the error message was printed out after > this message. nothing weird showed up with the rest of the output. i also > used telhttp to view the headers coming back from the script, and everything > looked fine. this error just seems to be leaking out, after processing the > script. Just because it appears one way on the command line doesn't mean it appears the same way on the server. It is pretty clear that, for whatever reason, the debug output is getting sent out before the headers are complete. That is not something Apache can or should work around. What is the exact output of running "scriptname | cat" from the commandline?
