Thanks for your quick reply.
I had already tried that, and it throws an error:
Invalid redirect path. Valid redirects are for example: /test/ or http://www.domain.tld/test/
Adding the full URL for the "Redirect Path" does seem to work, but then the L flag seems not to be respected, and the browser is forwarded to the http://www.domain.tld/home/
rather than staying on http://home.domain.tld/
This also seems to happen for any subdomain named with a root system folder name (etc, var, home). Further, creating a folder in the root with the name 'subdomain' triggers the same behaviour for any subdomains called 'subdomain'. This could cause issues, if many clients had a subdomain 'mail' and one day we created a root folder called 'mail' - it could get very messy.
Is this a bug? Should I report it on the bugtracker?