Details
-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Kromeriz 68
-
5
Description
Currently we create a new connection for each fragment request.
- Make use of info.magnolia.sitemesh.webapp.MagnoliaWebAppContext#decorate
-It looks like the connection is closed by tomcat after the first forward, making other fragments on the page to fail (reproducible with the integration test crawler).-
--Use WebContext.include() instead.- - Make sure the cache, variant resolver and model execution filters (all once per request filters) are triggered despite the fact that the forward is still the same request as original target.
Checklists
Attachments
Issue Links
- depends upon
-
MGNLPN-341 VariantResolverFilter is not triggered for forwards or includes
-
- Closed
-
-
MGNLADVCACHE-77 FragmentInjectionListener improvements
-
- Closed
-
-
MGNLCACHE-147 Cache filter is not triggered for forwards
-
- Closed
-
- is causing
-
MGNLEE-460 Adjust integration tests to changes in advanced cache and site mesh modules
-
- Closed
-
-
MSITEMESH-49 Remove workarounds for MAGNOLIA-6821 and MGNLADVCACHE-79
-
- Closed
-
- supersedes
-
MSITEMESH-43 Invalid security token if fragment is requested from another public instance
-
- Closed
-
-
MGNLCACHE-145 Provide a local scoped component which is able to influence caching
-
- Closed
-
-
MSITEMESH-47 DPC: Don't request URI if fragment is in cache
-
- Closed
-