-
Bug
-
Resolution: Fixed
-
Major
-
5.3.4
-
None
Original title:
404 page on public defined in web.xml: Triggering a 404 will render an empty white page
Everything described behaves this way only on a public instance. On Author instances all works fine.
Also all works perfect in 5.3.3, only in 5.3.4 this behavior appears.
Description:
Defining in the web.xml not a static docroot page, but a real Magnolia page.
For example:
<error-page> <error-code>404</error-code> <location>/demo-project/about.html</location> </error-page>
Calling a non existing page will return an empty white page (attention you must not be logged in!):
/demo-project/notExistingPage.html
Analysis:
It must be a problem of cache, most likely related to MAGNOLIA-5835
- It works on 5.3.3
- It works on 5.3.4 author (not caching)
- It works on 5.3.4 public when being logged in (not caching)
- It works on 5.3.4 public when adding a parameter (not caching)
/demo-project/notExistingPage.html?something - It is not working in 5.3.4 public when its is caching.
Also strange is:
Flushing the cache does not help.
No elements in cache, after request one element in cache, but the page is empty/blank.
Current work around:
- Use a static html page form the docroot. (just partially satisfying)
- caused by
-
MAGNOLIA-5835 Filters that extend from OncePerRequestAbstractMgnlFilter do not get run when there is a request.senderror
- Closed
- is causing
-
MAGNOLIA-6012 Ensure a page defined in 404-section of web.xml gets the channel
- Closed
- is cloned by
-
MAGNOLIA-6997 CLONE - OncePerRequestAbstractMgnlFilter must not be called twice (also in 5.5)
- Open