Am Do., 13. Sep. 2018 um 18:45 Uhr schrieb Stefan Seifert <
sseif...@pro-vision.de>:
>
> 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
>> 3. additionally make sure the JSP files of your application or that are
>> used from the platform do not contain calls to response.flush()!
>>
>>
>Yes, that's something we can validate and figure out, but I've seen this in
>too many cases, and not always a flush() was repsonsible. Also it's
HI Stefan,
Am Do., 13. Sep. 2018 um 18:16 Uhr schrieb Stefan Seifert <
sseif...@pro-vision.de>:
> hello jörg.
>
> we had a short discussion about this on our sling hackathon today:
>
> 1. check the configured response buffer size of the jetty engine that is
> currently configured for your
hello jörg.
we had a short discussion about this on our sling hackathon today:
1. check the configured response buffer size of the jetty engine that is
currently configured for your instance. if the response you expected is smaller
than the buffer size (in recent version this is 24KB i think),
Hi Jason,
Am Fr., 7. Sep. 2018 um 19:33 Uhr schrieb Jason E Bailey :
> Have you tried utilizing the var attribute in the sling:include tag?
>
>
> https://sling.apache.org/documentation/bundles/scripting/scripting-jsp.html#include
>
> That may be what you're looking for.
>
This might be a
