- From: Yaron Goland <yarong@microsoft.com>
- Date: Mon, 14 Apr 1997 18:12:20 -0700
- To: "'Gregory J. Woodhouse'" <gjw@wnetc.com>, Bob Denny <rdenny@dc3.com>
- Cc: Dave Kristol <dmk@research.bell-labs.com>, http-wg@cuckoo.hpl.hp.com
One could always invent a 1xx response which says "This current response just went south." Yaron > -----Original Message----- > From: Gregory J. Woodhouse [SMTP:gjw@wnetc.com] > Sent: Monday, April 14, 1997 9:46 AM > To: Bob Denny > Cc: Dave Kristol; http-wg@cuckoo.hpl.hp.com > Subject: Re: mid-course errors > > If CGI outgput is spooled, doesn't that defeat the purpose of chunked > encoding for CGI output? > > I share your concern about errors that occur after the 200 response. I > can't think of any way to signal a problem except to close the > connection > before the final chunk length of 0 is transmitted. This would work, of > course, but it would be nice if the server could give some indication > of > the nature of the problem. > > --- > gjw@wnetc.com / http://www.wnetc.com/home.html > If you're going to reinvent the wheel, at least try to come > up with a better one.
Received on Monday, 14 April 1997 19:48:48 UTC