[ https://issues.apache.org/jira/browse/SLING-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-2039: ------------------------------------- Attachment: SLING-2039-test.xml Simple test scenario for this issue. Upload attached file using curl: $ curl -u user:pass -F":contentType=jcr.xml" -F:operation=import -F:name=jcr-test -F:contentFile=@SLING-2039-test.xml http://host:port/apps Then send a request to /apps/jsp-test.html; e.g. with curl: $ curl -u user:pass http://host:port/apps/jsp_test.html If the server replies with a proper HTML response (ends with <html>) everything is fine. If the server replies with just a bunch of lower-case a characters then the error manifests itself. > Output lost with JSPs and sling:include > --------------------------------------- > > Key: SLING-2039 > URL: https://issues.apache.org/jira/browse/SLING-2039 > Project: Sling > Issue Type: Bug > Components: Engine > Affects Versions: Engine 2.2.2 > Reporter: Felix Meschberger > Assignee: Felix Meschberger > Fix For: Engine 2.2.4 > > Attachments: SLING-2039-test.xml > > > Using a single output buffer per included resource may lead to loss of > response data. > Consider this setup: > - main request handled by html.jsp. Some data is written to "out" > (buffering JspWriter) > - html.jsp incudes another jsp (list.html.jsp) which in turn writes more > data > - html.jsp continues writing to the output > If list.html.jsp sends less than the JspWriter's buffer, everything is fine. > As soon as the JspWritter buffer overflows, though, only the first bytes of > the actual response (exactly the size of the JspWriter buffer) is returned. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira