delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/10/15/01:02:41

Date: Thu, 15 Oct 1998 06:01:13 +0100 (BST)
From: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: djgpp AT delorie DOT com
cc: John Richter <john DOT richter AT yale DOT edu>
Subject: Re: DJGPP & CGI Problem
In-Reply-To: <Pine.SUN.3.91.981014115920.8710F-100000@is>
Message-ID: <Pine.OSF.4.05.9810150558420.1537-100000@sable.ox.ac.uk>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com

On Wed, 14 Oct 1998, Eli Zaretskii wrote:

> On Tue, 13 Oct 1998, John Richter wrote:
> 
> > IIS reports
> > 
> >     CGI Error
> > 
> >     The specified CGI application misbehaved by not returning a complete
> > set of
> >     HTTP headers. The headers it did return are:
> > 
> > Note that this same code works perfectly when I compile it using
> > CodeWarrior. This leads me to believe that there's something about
> > CodeWarrior's idea of printf is different from djgpp's idea of printf,
> > and IIS agrees with CodeWarrior.
> 
> I'm afraid it's much more serious than what you suspect.  This issue has 
> come up before and the conclusion was that it's impossible to get the 
> server to invoke a CGI application that is compiled with DJGPP.  I guess 
> the server opens a pipe to the CGI that is implemented in a way that 
> DOS programs don't support.

Maybe compiling the program with RSXNTDJ would help here?  If
you want, John, I can throw together a very simple RSXNTDJ
program that copies its stdin to its stdout, and send it to you
in binary format for testing (saves you the trouble of
downloading all of RSXNTDJ, in case it's not going to work...).

Of course, let me know if copying stdin to stdout isn't a
sensible way to test this; I don't know a lot about CGI
programming.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

xu do tavla fo la lojban  --  http://xiron.pc.helsinki.fi/lojban/lojban.html

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019