| -----Original Message-----
| I suppose you're talking about chunked encoding on the input ?
Yep.
| The current mechanism is not the best - we shouldn't use Content-Length,
| but let the connector signal the end of the stream.
Yes, exactly. Both request and the facade input stream take an
unknown content length to be an eof state. So, even if the data
is there, a servlet can't read it.
| Now the big question is when and where to make the changes. I don't feel
| very good about doing anything big for 3.3, at least not on Ajp13. I think
| we can do few fixes in the facade, with a lot of care.
I think ajp is handling the missing content length case OK, except we
might need to send an initial body chunk even if contentlength is not
specified.
I was hoping to get it in tc 3.3 since tc is not quite doing what one
would expect from reading the spec. How about I post a diff for review
and we go from there?
|It should. We need to fix this one for sure.
Done.
Thanks for your input!
Keith
