I have an OAuth flow that was previously working, but I just started getting mixed content errors and blocking Chrome.
Solved! Go to Solution.
Hello,
I had a look at this with our team and it looks like there was a quirk happening with the flow that specifically happens when a user is already logged in to Constant Contact and initiates the OAuth flow. After looking at this with the team that owns the affected application, we were able to find the cause and should be able to have the fix in place in the next couple of weeks.
For the immediate term, the solution to this problem is to simply try the flow again, as you should already be logged out of your account and see success on the second try. It's also worth noting that this does not impact all versions of Chrome, as I am not personally able to reproduce the problem on Chrome 44.0.2403.155.
If you have any questions, please let me know!
Sincerely,
Hello,
I had a look at this with our team and it looks like there was a quirk happening with the flow that specifically happens when a user is already logged in to Constant Contact and initiates the OAuth flow. After looking at this with the team that owns the affected application, we were able to find the cause and should be able to have the fix in place in the next couple of weeks.
For the immediate term, the solution to this problem is to simply try the flow again, as you should already be logged out of your account and see success on the second try. It's also worth noting that this does not impact all versions of Chrome, as I am not personally able to reproduce the problem on Chrome 44.0.2403.155.
If you have any questions, please let me know!
Sincerely,
Thank you for the prompt reply on a Friday afternoon, Elijah. I can work around this for a couple of weeks. :)
The holidays have come and gone. For many seasonal businesses, this means the rush of shoppers has decreased as well. Instead of turning off the lights and waiting for spring, make your email marketi...
See Article