Occasionally, some overzealous virtual uri mappings (specially regex based ones) interfere with magnolia functionality (e.g. recently mapping for ./features/. breaking export from features workspace in jcr tools and jcr browser.
Since VURIMs are meant for driving traffic of the public side of the website, I suggest we add bypass to VURIM filter for anything starting with /.magnolia and thus remove such conflicts before they can even occur.
Added benefit is that amount of virtual uri mappings will no longer affect performance of Admin Central.

Optionally, we could also document how to enable disable logging of virtual uri mapping execution and make sure we have descriptive log statement that could uncover similar issues where virtual uri mapping takes over control of request and drives it in potentially wrong direction.