-
Bug
-
Resolution: Fixed
-
Major
-
4.3.7
The magnolia filter chain is not executed on includes, therefor any wrappers that appear at the front of the request wrapper chain is not set using WebContext.push().
This means that when processing an include to a JSP that does an include of its own, using the request on the top of the request stack in WebContext, the include happens on the wrong wrapper.
A suitable test case for this would be a module with pages that return the word ERROR if they detect that the request wrapper stack in WebContext is not in sync. An integration test suite could then access these pages and test for the word ERROR.
This needs to be tested in all supported servlet containers / application servers.
See http://wiki.magnolia-cms.com/display/DEV/How+servlet+request+wrapping+works for more details.
- caused by
-
MAGNOLIA-2387 Request stored in WebContext is not updated after a forward/includes
- Closed
- is causing
-
MAGNOLIA-3748 An *update* should also apply conditions on web.xml (checking dispatchers for example)
- Closed
- is related to
-
MAGNOLIA-2010 WebContextImpl.include() should use pageContext if available
- Closed
-
MAGNOLIA-3337 Request Wrappers hide changes in upstream wrappers
- Closed
-
MAGNOLIA-2494 Add support for re-execution of filter chain on includes
- Closed
-
MAGNOLIA-1646 Makes jsp pageContext available in WebContext for use in paragraph renderers
- Closed
-
MAGNOLIA-3453 FreemarkerHelper does not expose Response object to freemarker
- Closed