Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
[ProxyConnect] Suddenly started looping when trying to log in
judgej
✭
Until today, my ProxyConnect has been working fine. It has suddenly stopped working and I am wondering if anyone has encountered this.
I have checked the code is the same as it was a few days ago (when it was working), so I am beginning to suspect some state in the database has knocked it out.
When a user tries to go to /discussions overview while not logged in, ProxyConnect redirects them to /projecttalk/entry/signin?Target=discussions
This then redirects them to the CMS login page. That login page realises they are already logged in, so redirects back to Vanilla, and then the whole process starts again. The browser just appears to load for a minute, then (presumably after its maximum number of 302 redirect attempts) gives up.
At no point does the "authorisation URL" get checked, which would tell Vanilla that the user is logged in already.
If this is a new user, the user does not get created in Vanilla like they were a few days ago.
Could this be caused perhaps by some pollution of the browser cookies? The key here is that all the code looks the same as it did a few days ago when it was working perfectly, and it has been logging me in and out flawlessly for weeks.
I have checked the code is the same as it was a few days ago (when it was working), so I am beginning to suspect some state in the database has knocked it out.
When a user tries to go to /discussions overview while not logged in, ProxyConnect redirects them to /projecttalk/entry/signin?Target=discussions
This then redirects them to the CMS login page. That login page realises they are already logged in, so redirects back to Vanilla, and then the whole process starts again. The browser just appears to load for a minute, then (presumably after its maximum number of 302 redirect attempts) gives up.
At no point does the "authorisation URL" get checked, which would tell Vanilla that the user is logged in already.
If this is a new user, the user does not get created in Vanilla like they were a few days ago.
Could this be caused perhaps by some pollution of the browser cookies? The key here is that all the code looks the same as it did a few days ago when it was working perfectly, and it has been logging me in and out flawlessly for weeks.
0
Comments
So IE has something that has changed. I'll delete the cookies one by one and see if one of those was causing trouble.
IE is not exactly helpful in allowing you to look at cookie details, so I cannot say what it was, but watch that space - something is going on in there. It could even be down to cookie lifetimes, with perhaps the CMS cookie being renewed? Dunno, perhaps this will all mean something to someone.
I'm on Vanilla 2.0.14 and ProxyConnect 1.8.4