[TOMAHAWK-1177] ExtensionsFilter should not buffer data for certain content-types

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.1.6
• Component/s: ExtensionsFilter
• Assignee: Unassigned
• Reporter: Simon Kitching
• Created: 17/Jan/08 11:41
• Updated: 25/Mar/19 16:11

Description

Currently, ExtensionsFilter arranges for all data generated by a request to be buffered. Then after the request is complete it checks the content-type http header and skips any further processing if the type is not "text/html" or similar.

Maybe the response-wrapper class could catch the start of response data writing, check its headers (which will be complete at that time) and then for non-html responses just stream the data directly rather than buffer it. This will save time and memory usage when a request to a .jsf url causes a non-html response to be returned. This isn't very often, but sometimes people do generate pdfs etc as a result of a jsf postback.