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

Hi, If you define your url before the admin, it might get your view instead. (I _think_ it will work, though I may be totally wrong.) Collin On Wednesday, December 3, 2014 2:02:42 PM UTC-5, Tim Chase wrote: > > On 2014-11-30 11:04, Collin Anderson wrote: > > As of django 1.7, the admin will

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

On 2014-11-30 11:04, Collin Anderson wrote: > As of django 1.7, the admin will redirect to a separate login page > (whatever url reverse('admin:login') returns). > > https://github.com/django/django/commit/be0ad62994a340ad54a0b328771931932a45a899 Shouldn't this reach for

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

Hi, As of django 1.7, the admin will redirect to a separate login page (whatever url reverse('admin:login') returns). https://github.com/django/django/commit/be0ad62994a340ad54a0b328771931932a45a899 You could use a middleware to do an earlier, more straightforward require login. Collin On

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

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