Just a simple question a co-worker made, and it really made me think about: "why Magnolia stops even the requests it can't handle and returns a 404 and not pass it to the next filter in chain?" I didn't find a good answer to this simple question, so maybe I'm missing some structural defition about Magnolia. There are the bypasses to exclude some of the requests you can actually classify in some pattern, but there is no way to say if a generic request will be really handled by Magnolia. Would be possible to add some sort of "404Voter", or some other way to say to Magnolia "if you cannot handle it just let it go to the next filter in chain"? I don't know if a voter like this is possible because bypasses voting should happen before actual rendering, but at least adding an attribute to the last rendering filter should be possible. This seems unuseful in a standard environment where Magnolia is the one and only filter, but I started to find it useful in complex environment with many overlapping filters.
Regards, Danilo. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
