Re: mid-course errors

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Dave Kristol: "SSL tunneling status"
• Previous message: Dave Kristol: "mid-course errors"
• Maybe in reply to: Dave Kristol: "mid-course errors"
• Next in thread: Gregory J. Woodhouse: "Re: mid-course errors"
• Reply: Gregory J. Woodhouse: "Re: mid-course errors"

OK, don't laugh... For CGI, WebSite spools the output by default (you can 
disable it) into a file which is implemented as a privately backed block of 
expandable virtual memory. This has a few advantages and the obvious CPU/disk 
hit and reduction of capacity. The advantages are (1) you can rewind the 
output stream and send a non-200 response at any time, and (2) Keep-Alive is 
retained without chunking because you can get the content-length. The latter 
"advantage" will fade with time, of course.

  -- Bob

On Apr 14, Dave Kristol wrote:
> Subject: mid-course errors
> Here's something that has puzzled me about HTTP server
> implementations.  What happens if the server encounters an error after
> it sends, say, a "200 OK" response and part of the entity body?

• Next message: Dave Kristol: "SSL tunneling status"
• Previous message: Dave Kristol: "mid-course errors"
• Maybe in reply to: Dave Kristol: "mid-course errors"
• Next in thread: Gregory J. Woodhouse: "Re: mid-course errors"
• Reply: Gregory J. Woodhouse: "Re: mid-course errors"