[MAGNOLIA-5416] Add support for handling non-renderable requests Created: 24/Oct/13  Updated: 10/Dec/13  Resolved: 25/Nov/13

Status: Closed
Project: Magnolia
Component/s: rendering
Affects Version/s: 4.0
Fix Version/s: 5.2.1

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-1432 security: cache can go round security... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Date of First Response:
Sprint: 5.2-rc1, 5.2.1

 Description   

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.


 Comments   
Comment by Tobias Mattsson [ 22/Nov/13 ]

This was not merged to master and is not present in 5.2.

Generated at Mon Feb 12 04:04:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.