Re: Nasty chunking bug (in MSIE?) when using ap_rwrite()/ap_rflush()

TOKILEY@aol.com wrote:

>In a message dated 01-07-16 18:16:37 EDT, Ian Holsman wrote...
>
>>On 25 Jun 2001 12:13:51 -0400, Bill Stoddard wrote:
>> > I have a module that calls ap_rwrite() followed by ap_rflush(). Content
>>length is not
>> > provided so Apache 2.0 chunks the response.
>> >
>> > Here is what happens...
>> > I call ap_rwrite() to write a x75 len byte stream. All the correct
>>headers are built, and
>> > the content is buffered by the OLD_WRITE filter. Then I call ap_rflush()
>>which causes the
>> > headers to be sent on the wire along with the first chunk (x75 length).
>>
>My
>
>>handler is done
>> > at this point and returns control to Apache. The next thing Apache
>>
>sends
>
>>on the wire is
>> > the 0 byte chunk header to indicate that the response is done.
>> >
>> > The problem: IE chokes when it receives just the 0 byte chunk header in
>>
>a
>
>>packet.
>> >
>> > Thoughts?
>> >
>> > Bill
>>
>>
>> hi Bill,
>> I was wondering if you got anywhere with this
>> I'm seeing this with mod_proxy at the moment.
>>
>> my inital thought was to put some logic in the chunking filter
>> just not to send the 0 byte chunk out.. can you see anything barfing
>> on this?
>>
>> what do you think?

MSIE is choking due to a '0' byte happening in the middle of the response being sent back.

I think this is due to the proxy code sending a EOS bucket after the subrequest. (it doesn't happen with non-proxied requests), hopefully it will be easy to find.

>
>
>I would find it hard to belive that a modern browser would
>screw up a chunking byte length appearing all by itself
>at the top of a new packet ( Even though that's highly
>unusual... usually it's right at the end of the data in
>the same final data packet ).
>
>Kevin Kiley
>

..Ian Received on Tue Jul 17 01:55:53 2001