Currently RenderingFilter is terminal. It doesn't allow any requests past itself forcing configuration of bypasses for further processing (where possible) or adding filter before rendering and wrapping and checking response on it's way back to find out if page was rendered or not which is limiting in several ways, e.g.:
- bypasses can be configured only based on URI path, but not on the fact whether rendering filter finds the resource to render or not.
- post processing in filter on it's way back through filter chain adversely affects streaming of the response and adds overhead to EACH request thus limiting the performance.