Re: [1.3 PATCH^H^H^H^H^HBUG] chunked encoding problem

I'm sure there's a great reason for setting B_EOUT flag here, but it sure does suck if you have data waiting to be sent to the client since setting B_EOUT convinces ap_bclose() not to write any more data. It is only set when the connection is aborted or the fd is gone, both indicating that we

Re: [1.3 PATCH^H^H^H^H^HBUG] chunked encoding problem

On Friday, October 18, 2002, at 07:44 PM, Roy T. Fielding wrote: I'm sure there's a great reason for setting B_EOUT flag here, but it sure does suck if you have data waiting to be sent to the client since setting B_EOUT convinces ap_bclose() not to write any more data. It is only set when

[1.3 PATCH^H^H^H^H^HBUG] chunked encoding problem

I'm sure there's a great reason for setting B_EOUT flag here, but it sure does suck if you have data waiting to be sent to the client since setting B_EOUT convinces ap_bclose() not to write any more data. In trying to recreate a real world problem, I am using a handler that does ap_rwrite(1