httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter J. Cranstone" <cransto...@msn.com>
Subject RE: c-l filter and buffering of the entire response
Date Wed, 03 Jul 2002 12:04:24 GMT
Couple of thoughts...

1. What if the content is compressed.
2. What about compressed chunked encoding.
3. What if servers start supporting compressed headers. RFC 1144

Regards,


Peter

-----Original Message-----
From: trawick@rdu88-250-182.nc.rr.com
[mailto:trawick@rdu88-250-182.nc.rr.com] On Behalf Of Jeff Trawick
Sent: Wednesday, July 03, 2002 5:55 AM
To: dev@httpd.apache.org
Subject: c-l filter and buffering of the entire response

c-l filter thinks that a partial send is not okay if using HTTP
0.9. connection->keepalive is AP_CONN_UNKNOWN.  If this were set to
AP_CONN_CLOSE, c-l filter would allow a partial send.  I dunno what
else that would break.

Right now Apache is eating lots and lots of storage on a big CGI
response on HTTP 0.9 request.  The entire response is getting
buffered.

With HTTP/1.0, the entire response is getting buffered too.  Do we
absolutely have to get the content length, or can we set connection
close and omit the content length field?

(Haven't we been through this before?)

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...

Mime
View raw message