we’re using the native 40x error handling from this release note. This configuration just renders the 404 page in the currently not found page. But I want to archive that the user will be redirected to the real 404 page. Is that possible?
I would appreciate it if somebody can help me with this problem.
Thanks for your answer Christoph, but this is the same code from the release nodes (the link that I mentioned yesterday). The Neos.Fusion:Renderer just renders the 404 page into the current one and that’s not what I want. I need a real redirect to the 404 page.
Because we have a frontend login and therefor protected pages. If you are not logged in and try to access a protected page you will get a 404 notification. For this specific behaviour our marketing wants a redirect to the login page.
I have to archive that the standard 404 errors act like before. But 404 errors of protected pages have to be redirected to the login page.
After hours of Google research, this is my current configuration:
Unfortunately this does not work, it acts every time like a normal 404 (page not found) error. I think that the part of the condition that checks the instance does not work, because the page (node) object is never present.
The next error is that the «My.Website:ProtectedRedirect» is not working. If I use this configuration…
You could keep some kind of protected list of pages with their urls in a persistent cache that gets updated when a document node is updated. And you verify the url in the 404 handler.
Nothing else comes to my mind right now, sorry.