Skip to main content

Replied to a post on github.com :

At the moment it doesn't.

I did originally include the login page on deniedContent, which worked, but 1) looked horrible ;) and 2) there's a case for having one page for login as a central point to override.

I was thinking about this on the way home from training, and I think maybe a good approach would be a "soft" redirect on deniedContent (window.location or meta refresh). That would preserve outward behaviour for users, but would mean you *would* get the correct HTTP error code back.