Unico Hommes wrote:
Rogier Peters wrote:
Guys,
On 18/5 Joerg asked a question about invalid content length errors[1] due to
readers. There is also a bug that is somewhat related[2], but it seems to be
WONTFIX.
The WONTFIX seems to apply to the original description of the bug only. There is a related issue that is mentioned in that thread that I think *is* a valid problem.
I have the following case :
generator reader | | validator .. dtd | serializer
In this case the reader sets the content-length, and the serializer doesn't. So
if the length of the serializer's output is greater than that of the dtd, output
is incomplete.
Althoug a quick fix is not to get the dtd through a reader, I'm sure there are
cases where that isn't a solution. I didn't post this as a bug, yet, because I am not sure whether this is just
unintended use of the reader.
It oughta work. I don't see how it doesn't.
Oh I see now. The ResourceReader also sets the content length on the response. It *really* shouldn't do that IMHO. Anybody know why it does that?
-- Unico
