Hi
> It is a dirty Tomcat specific trick that will only work as long as the code
> is the way it is but if you throw a ClientAbortException wrapped
> in a ServletException you shouldn't see that log message.
Thanks a lot, this was just what I was looking for.
Regards,
Steffen
smime.p7s
On 03/06/2016 22:08, Steffen Heil (Mailinglisten) wrote:
> Hi
>
>
>> throw new ServletException();
>
> That was the difference. I threw a IllegalStateException(), so tomcat sent
> "0\r\n".
> I changed my code to throw a ServletException() and now it works.
> Thanks for that.
>
>
> One very l
Hi
> throw new ServletException();
That was the difference. I threw a IllegalStateException(), so tomcat sent
"0\r\n".
I changed my code to throw a ServletException() and now it works.
Thanks for that.
One very little thing left: Is there a way to suppress the logged exception:
Jun 03, 2016
On 03/06/2016 15:14, Mark Thomas wrote:
> On 01/06/2016 23:08, Steffen Heil (Mailinglisten) wrote:
That's another story.
I tried that. And the internet explorer as well as curl report an error,
if the download stops without the ending 0\r\n.
But I had to set "Connection: c
On 01/06/2016 23:08, Steffen Heil (Mailinglisten) wrote:
>>> That's another story.
>>> I tried that. And the internet explorer as well as curl report an error, if
>>> the download stops without the ending 0\r\n.
>>>
>>> But I had to set "Connection: close" and "Transfer-Encoding: chunked"
>>> mys
Hi
> > Yes, we thought about that. However it still leaves the problem of a
> > lot of storage on the server that is used for no reason and increasing
> > the time to download the backup..
> So it's better to buffer the huge download in memory instead of on the disk?
> Maybe I don't understand t
> > That's another story.
> > I tried that. And the internet explorer as well as curl report an error, if
> > the download stops without the ending 0\r\n.
> >
> > But I had to set "Connection: close" and "Transfer-Encoding: chunked"
> > myself and encode the chunk headers myself.
> > If I leave t
