Hi Anthony
AFAIK the status goes first with the 1st write, so there's really no way
to replace it with something else if there was an error later on while
writing the stream.
I don't think so the fact a client gets 200 and then, presumably,
IOException, is inconsistent, the client code reading the data directly
from the input stream always has a catch for IOException, it can be
thrown even if there were no errors on the server side when writing it...
Sergey
On 13/10/17 12:30, MULLER, Anthony wrote:
Hello,
I have a REST call which returns a generated ZIP output. But during generation,
an issue may occurred... However, the client seems to receive a HTTP code 200
with a corrupted ZIP.
Is it possible to do better? Is this case managed by HTTP protocol? By CXF?
Best regards,
Anthony
