User Agent: Mozilla/5.0 (Windows NT 6.1; rv:20.0) Gecko/20100101 Firefox/20.0 (Beta/Release) Build ID: 20130326150557 Steps to reproduce: https://moztrap.allizom.org/runtests/admin Actual results: Page not found (404) Request Method: GET Request URL: https://moztrap.allizom.org/runtests/admin Using the URLconf defined in moztrap.view.urls, Django tried these URL patterns, in this order: ^$ [name='home'] ^runtests/ ^$ [name='runtests'] ^runtests/ ^environment/(?P<run_id>\d+)/$ [name='runtests_environment'] ^runtests/ ^run/(?P<run_id>\d+)/env/(?P<env_id>\d+)/$ [name='runtests_run'] ^users/ ^manage/ ^results/ ^admin/ ^browserid/ ^api/ ^owa/ ^media\/(?P<path>.*)$ The current URL, runtests/admin, didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. Expected results: For any such irregular url patterns i expect this project/product to redirect every one/user to login page . Security shall be strong by doing so preventing users from entering wrong url patterns.
Summary: "unclear error message"? → Unclear error message
Going directly to an url that doesn't exist does not provide the user with a clear error message, nor does it redirect to valid page such as the home page.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.