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 som
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 instanc
gt;To: users@sling.apache.org
>Subject: [Discussion] | should buffer output in memory
>
>In my sling application I have a number of nested components, which are
>called via the tag. If a component late in the rendering
>process throws an error, I would like to return an HTTP statuscode 500. But
>
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 workaro
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.
- Jason
On Fri, Sep 7, 2018, at 1:18 PM, Jörg Hoh wrote:
> In my sling application I have a number of nes
In my sling application I have a number of nested components, which are
called via the tag. If a component late in the rendering
process throws an error, I would like to return an HTTP statuscode 500. But
if more data than the size of the output buffer are written, the response
headers are already
