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.
I have the following case :
generatorreader
| |
validator .. dtd
|
serializer
In this case
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
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
Unico Hommes wrote:
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?
I see that EnvironmentWrapper ignores set content length. And it has
RequestWrapper. BUT IT DOES NOT HAVE ResponseWrapper! I
Vadim Gritsenko wrote:
Unico Hommes wrote:
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?
I see that EnvironmentWrapper ignores set content length. And it has
RequestWrapper. BUT IT DOES NOT HAVE
Vadim Gritsenko wrote:
Unico Hommes wrote:
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?
I see that EnvironmentWrapper ignores set content length. And it has
RequestWrapper. BUT IT DOES NOT HAVE
Unico Hommes wrote:
Vadim Gritsenko wrote:
Unico Hommes wrote:
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?
I see that EnvironmentWrapper ignores set content length. And it has
RequestWrapper.
Vadim Gritsenko wrote:
Unico Hommes wrote:
Vadim Gritsenko wrote:
Unico Hommes wrote:
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?
I see that EnvironmentWrapper ignores set content length. And
Unico Hommes wrote:
Vadim Gritsenko wrote:
Unico Hommes wrote:
Vadim Gritsenko wrote:
Unico Hommes wrote:
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?
I see that EnvironmentWrapper ignores set
Vadim Gritsenko wrote:
Unico Hommes wrote:
Vadim Gritsenko wrote:
Unico Hommes wrote:
Vadim Gritsenko wrote:
Unico Hommes wrote:
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?
I see that
On 21.05.2004 21:36, Joerg Heinicke wrote:
Can anybody tell me what can cause the invalid content length?
Found at least the reason: A stylesheet is imported via cocoon:/ and in
this pipeline the stylesheet is *read* from disk, the ResourceReader
also sets the content-length header, the 919 bytes
cocoon.processPipelineTo(). Shouldn't this give hints on the root
of the problem?
Joerg
On 21.05.2004 21:36, Joerg Heinicke wrote:
On 18.05.2004 23:56, Joerg Heinicke wrote:
Can anybody tell me what can cause the invalid content length? The
first one is html serializer, the latter ones text serializer.
Found
On 18.05.2004 23:56, Joerg Heinicke wrote:
Can anybody tell me what can cause the invalid content length? The
first one is html serializer, the latter ones text serializer.
Found at least the reason: A stylesheet is imported via cocoon:/ and in
this pipeline the stylesheet is *read* from disk
Can anybody tell me what can cause the invalid content length? The first
one is html serializer, the latter ones text serializer.
Joerg
23:45:16.828 WARN!! Invalid length: Content-Length=1043 written=798 for
http://127.0.0.1:/xfaces/test-html-mozilla-skin-simple
23:45:18.000 WARN!! Invalid
We were seeing this when putting up an error page. Mysteriously, we
changed our error page and it went away. No idea why.
Ralph
Joerg Heinicke said:
Can anybody tell me what can cause the invalid content length? The first
one is html serializer, the latter ones text serializer.
Joerg
23
On 18.05.2004, at 23:56, Joerg Heinicke wrote:
Can anybody tell me what can cause the invalid content length? The
first one is html serializer, the latter ones text serializer.
Joerg
another one is http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17370
/leo
16 matches
Mail list logo