true...  I was thinking that your header might not be complete and it was
the header, not the status code, that was causing the problem.  I assumed
your browser was seeing the script output ok...

Hmmm...

> -----Original Message-----
> From: Jim Serio [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 02, 2000 2:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: No Status From Server
> 
> 
> I was going to post that but I though PerlSendHeader
> was just responsible for the Content-type and not the
> status code. In either case, I have PerlSendHeader Off.
> 
> Jim
> 
> > 
> > are you using 
> >    PerlSendHeader On
> > in your httpd.conf?
> > 
> > maybe that will help?
> > 
> > --Geoff
> > 
> > > -----Original Message-----
> > > From: Jim Serio [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, February 02, 2000 2:18 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: No Status From Server
> > > 
> > > 
> > > I'm setting up a local monitoring service using SiteScope
> > > from Freshwater Software. When I put in an URL for one
> > > of my cgi-perl scripts, the monitor comes back with the
> > > following error:
> > > 
> > > no status in reply from server
> > > 
> > > Static pages and standard cgi script work fine, so I
> > > am assuming that my scripts (or mod_perl) is not sending
> > > a Status OK to the browser. Do I have to send this via
> > > my script or am I missing something obvious?
> > > 
> > > Jim
> > > 
> > 
> 
> 
> -- 
> Jim Serio - [EMAIL PROTECTED]
> Producer, World of Coasters
> 

Reply via email to