httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: [PATCH] nph killer, cgi buffering (take 3)
Date Mon, 21 Jul 1997 20:10:42 GMT
nph- CGIs were not compatible with HTTP/1.1 or SSL support because they
were passed a socket that talked directly to the client.  As such they
would have to implement the transport level details such as encryption or
chunking in order to work properly.  This isn't part of the CGI spec so
CGIs generally don't do this.  The most common use of nph- CGIs is when
the programmer wants an unbuffered connection to the client; regular CGIs
have always been fully buffered.  Apache now provides an unbuffered
connection to all CGIs.  Given that most CGIs are written in a language
that by default does buffering (i.e. perl) this shouldn't have a
detrimental effect on performance.  The programmer can still use nph-
CGIs, and they're still responsible for sending valid HTTP/1.1 responses. 

How's that? 


On Mon, 21 Jul 1997, Marc Slemko wrote:

> On Sat, 19 Jul 1997, Dean Gaudet wrote:
> >  Changes with Apache 1.3
> > -  
> > +
> > +  *) nph- CGIs were not compatible with HTTP/1.1 or SSL support.  They
> > +     now are; provided the cgi does all the right protocol work itself,
> > +     which is not recommended at all.  Instead regular CGIs now have
> > +     far more control over the buffering between them and the client.
> > +     Apache will flush output to the client whenever it would have to
> > +     block while reading from the CGI.
> > +     [Dean Gaudet, Roy Fielding, Sameer Parekh]
> > +
> I don't understand.  Your wording isn't particularily clear and seems
> disjointed.  Clarify?

View raw message