Re: 1. File transfer, client->server; 2. Problem with popen in CGI script.

• Mail folder: WWW Talk Apr 94-present
• Next message: ts: "1. File transfer, client->server; 2. Problem with popen in CGI script."
• Previous message: Ernesto_Nebel.sd@xerox.com: "1. File transfer, client->server; 2. Problem with popen in CGI script."
• Maybe in reply to: Ernesto_Nebel.sd@xerox.com: "1. File transfer, client->server; 2. Problem with popen in CGI script."
• Reply: ts: "1. File transfer, client->server; 2. Problem with popen in CGI script."

Errors-To: listmaster@www0.cern.ch
Date: Sat, 30 Apr 1994 22:53:24 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <"30-Apr-94 13:50:39 PDT".*.Ernesto_Nebel.sd@Xerox.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: Ernesto_Nebel.sd@xerox.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: Ernesto_Nebel.sd@xerox.com
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: 1. File transfer, client->server; 2. Problem with popen in CGI script.
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

Clarification:

On the popen problem, when I said:

"If I delete every "%c" and ",10" from the code above, the user DOES see the
response appear in his/her Mosaic browser, but of course, the ftp command
fails."

I meant every %c in the fprintf commands.  The %c's in the printf commands
stay.  So it is only the newlines in the fprintf commands, that get sent to
ftp, that fail.

Ernesto