Am Do., 13. Sep. 2018 um 18:45 Uhr schrieb Stefan Seifert < [email protected]>:
> > yes, but currently we are quite convinced that if you have some places in > the response rendering (e.g. JSP pages) that do a manual flush, there is no > chance the prevent the problem you describe, only with hacks like mocked > requests to avoid the flush command hits the servlet engine. not sure if we > really should go this way. we assume (have not tested it) the proposal you > describe will not help if there are still flush() calls in the code. > Sure. I will try with a filter and some mock response object wrapping the original one. Jörg -- Cheers, Jörg Hoh, http://cqdump.wordpress.com Twitter: @joerghoh
