Nothing says I have to apply the tag like, right now. Within a few days should be fine if I understand the whole rollup idea.

We can take the time to fix this. That's the point of a rollup release. Besides, there may be several things to fix here.

The read body loop in ap_proxy_http_handler() is wrong, but not always. Never gets EOS?

The ap_dechunk_filter() seems to not implement all of Sec. 19.4.6 of RFC 2616.

If as RFC 2616 says the proxy must dechunk, do we have to reassemble the chunked body into something with a valid Content-Length:? We don't have this data until the end of the chunked body out of the dechunk filter. This means we have to buffer the body 'till we can finish sending the header data. Yuck.

Akamai's servers for the apple site are running apache-1.3.9/macosx. It's our own dog food. Is there a compatibility issue between us & them (likely us 8^)?

Chuck

On Thursday, July 19, 2001, at 10:12 PM, Ian Holsman wrote:

Chuck Murcko wrote:


On Thursday, July 19, 2001, at 06:01 PM, Ian Holsman wrote:

seeing how people are tagging/building the next .21 beta
do we want this patch applied?
as AS IS using IE and HTTP/1.1 is kinda hosed.




One more try...my mail is bad today.

+1 as long as we fix the real problem for release.

by the looks of further playing with this patch, it doesn't fix all problems.
for instance.. the apple.com/macosx is hosed.



Chuck Murcko Topsail Group http://www.topsail.org/



Reply via email to