Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 5890 invoked by uid 6000); 31 Jan 1999 12:57:06 -0000 Received: (qmail 5883 invoked from network); 31 Jan 1999 12:57:05 -0000 Received: from drawbridge.eu.c2.net (194.152.70.22) by taz.hyperreal.org with SMTP; 31 Jan 1999 12:57:05 -0000 Received: from ecstasy.localnet ([192.168.2.4]) by drawbridge.eu.c2.net with smtp (Exim 1.92 #3) for new-httpd@apache.org id 106wXT-0000x8-00; Sun, 31 Jan 1999 13:03:47 +0000 Date: Sun, 31 Jan 1999 12:57:57 +0000 (GMT) From: Paul Sutton To: Apache Subject: Re: [Win32] CGI batch file problem? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Sat, 30 Jan 1999, Marc Slemko wrote: > On Sat, 30 Jan 1999, Paul Sutton wrote: > > Erm, something seems to be up with CGI execution of batch files, unless > > I'm doing something strange. > > Why do you think the behaviour you are seeing is odd? > > What you are probably getting from the .bat file is a blank line, then > the output you see to the client. A blank line terminates the CGI > headers, which happen to be empty. The rest is what you should get. Yeah, you are right, the blank line at the start of output is actually part of the script output. I assumed it was part of the interactive shell. So "echo" mode in a batch file doesn't just echo the commands, it also echo a blank line before echoing each command to be executed. Paul