Yes, should have mentioned that you should use PAP.
From the customizing manual:
request for "/login" page
if user has successfully logged in (or is already logged in), alogin.html is displayed; if alogin.html is not found, redirect.html is used to redirect to the originally requested page or the status page (in case, original destination page was not given)
So the login.html submits to /login and the login is successfully processed. If alogin.html exists it will be displayed, in my above example that alogin.html redirects to Google. If it doesn't exist then redirect.html either redirects to the originally requested URL, or the status page if that isn't available. In this scenario it wouldn't be as the login.html you're using doesn't perpetuate that variable.
Sounds like your alogin.html doesn't exist, is named wrong, something. Therefore redirect.html is shown, the originally requested URL is not available, so the status page is shown. Fix your alogin.html and you should be fine.
This works peachy for me for tens of thousands of users. As long as alogin.html exists and shows something sensible (including a redirect to Google) there won't be a status page.