Sunday, November 30, 2014

Re: Test client to a redirect requiring a login doesn't set redirect_chain properly? [2nd follow-up]


As of django 1.7, the admin will redirect to a separate login page (whatever url reverse('admin:login') returns).

You could use a middleware to do an earlier, more straightforward require login.


On Friday, November 28, 2014 7:46:05 AM UTC-5, Tim Chase wrote:
On 2014-11-27 20:32, Tim Chase wrote:
> As a bit of follow-up information, if I use runserver and browse to
> the view, it redirects me to /admin/common/region/add/ but it
> displays as the login screen.  Am I missing why this wouldn't do a
> redirect to my named login URL?

A careful reading of [1] suggests that the admin provides its own
login page via the login_template setting: "Path to a custom template
that will be used by the admin site login view."  It apparently
renders this at the URL of the destination page rather than
redirecting to the regular (contrib.auth or some named auth-URL) and
providing a "next={{original_url}}"

Is there any way to get the admin to just use the contrib.auth login
page that I already have in place?



You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

No comments:

Post a Comment