Alexander Klimetschek wrote:
Grzegorz Kossakowski schrieb:
That's weird. Any clue about that?
The problem is a missing HTTP status code when the response is
committed. This happens due to Reinhard's change for the dynamic setting
of the status code (see below), that I just got when updating to your
servlet changes. When putting these lines back into the code, the
exception disappears.
There is a bug in my code that led to "null" values instead of -1. I hope that
fixes the problem.
Does anybody know why we set -1 by default instead of 200?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
