Hi Mark
crisb> P.S.: If a documentation update is recommended,
crisb> I would be happy to make the changes,
crisb> but I would probably need guidance for that too. ;-)
markt> Source file is here:
markt> https://github.com/apache/tomcat/blob/main/webapps/docs/config/http.xml
markt> A pull reques
On August 10, 2021 8:00:45 AM UTC, Marcin Wisnicki wrote:
>However I've noticed that in Tomcat the behaviour can only be achieved
>by throwing an exception before close.
>If I don't throw and simply return or call close before exception
>Tomcat will write terminal '0'.
>
>Is there a way to trigger
To make repro easier:
https://gist.github.com/mwisnicki/6df71b2b5f7712306fca27bf34c24e94
On Tue, 10 Aug 2021 at 04:00, Marcin Wisnicki wrote:
>
> However I've noticed that in Tomcat the behaviour can only be achieved
> by throwing an exception before close.
> If I don't throw and simply return or
However I've noticed that in Tomcat the behaviour can only be achieved
by throwing an exception before close.
If I don't throw and simply return or call close before exception
Tomcat will write terminal '0'.
Is there a way to trigger immediate close without that write('0')
without using exceptions
Thanks, it seems like it must be one of Spring Boot's filters breaking
it. I should've tried without it first, mea culpa.
In a pure tomcat container it works as you described whereas with
Spring something inserts final 0 so the aborted connection looks like
a valid chunked response to clients.
I'l
