|
Mike Looijmans
nlv11281 at natlab.research.philips.com
Fri Jun 30 07:56:25 EDT 2006
Well, the HTTP RFC says that the server is free to close the connection at any time. The "lost" request in the pipeline is the client's responsibility then - the keep-alive is only supported if the server sent a response to the request but didn't include a "Connection: Close" header in the response - and even then, the server may still close the connection. IE since version 4.0 supports this just fine. Only netscape (up to 6.0) used to fail on this particular test. Mike Looijmans Philips Natlab / Topic Automation Graham Dumpleton wrote: > > On 14/06/2006, at 11:01 PM, Jim Gallacher wrote: > >> Apache gives your handler a pointer to the incoming file stream and >> it then becomes the responsibility of the handler to deal with it. If >> no handlers consume the stream it gets discarded (I assume). > > > Yes discarded, although that can entail still reading it from the > client socket > because of fact that HTTP 1.1 allows pipelining of requests and thus there > may be a request following the data which has to be handled and Apache > has to be able to get to that. Thus for large content, Apache may still > have > to read it even if not used and therefore resources (time) will be > consumed in > doing so. > > Graham > > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://mailman.modpython.org/mailman/listinfo/mod_python > -- Mike Looijmans Philips Natlab / Topic Automation
|