Fixed #24713 -- Redirect loop detection in test client is incorrect

[mounirmesselmeni]

Raising RedirectCycleError only when already on the same view more than twice.
If the count should be other than 2 please let me know.

[timgraham]

A test is also needed.

[timgraham]

Not sure why you closed the pull request -- do you plan to complete it or did you abandon the issue?

[mounirmesselmeni]

After what we discussed on Google group I think the issue need to be reviewed may be it does not make sense to fix it because of the usage example shown on the ticket.

[timgraham]

I didn't think we reached that conclusion. Could you explain why?

[mounirmesselmeni]

Yes, first thing making multiple redirect for a client I don't think it's 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 thing 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.

[timgraham]

I agree that the use case seems a bit obscure. I asked for further details from the reporter on the ticket. Thanks.