#24713: Redirect loop detection in test client is incorrect
-------------------------------------+-------------------------------------
Reporter: agmathew | Owner:
Type: Bug | Status: new
Component: Testing framework | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: redirect loop | Triage Stage: Accepted
detection test client |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
From Mounir on the pull request:
I don't think making multiple redirects for a client is the right way.
Let take an example: A user is trying to access a home page "/home" and
the server need to update an information, let's say a last_visit datetime
field or something else -- do we need to redirect him to "/update" make
this update and redirect him again to "/home"? I think it's better to run
a signal, an asynchronous task, make the update by calling a model method
or something else or even do the logic from the "/home" view. If we are
not sure that this is a common issue for many (now it look like only one
person have this problem) I think it's better to keep things like they
are.
I'd agree with this. Is there a reason you can't restructure your code to
avoid the redirect? See also the [https://groups.google.com/d/topic
/django-developers/8oXwD_KGjvc/discussion discussion on the django-
developers mailing list].
--
Ticket URL: <https://code.djangoproject.com/ticket/24713#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.d1dae1766d07d0b9688ae737496061d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
