Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Reproducible with the following setup:
1. Use secure pages module to secure some of your paths
2. Now to avoid mixed content warnings, you should set your /mollom/* paths to use https too for the benefit of those pages.
3. However, if you still have a form mollom enabled on a non-https page, when switching to audio, the client code only gets a redirect (which it does not handle).
Result: audio captcha will not replace the image captcha, despite repeated cycling clicks on the image/audio captcha links.
Comments
Comment #1
sunSorry, but I'm a bit confused here.
Hence, if the originating (parent) page is on SSL, then also this request is on SSL. And vice-versa.
Therefore, I don't quite understand why you have to manually configure /mollom/* paths to force them to use HTTPS in the first place?
Comment #2
sunSo I think this entire issue boils down to the question why HTTPS is enforced for /mollom/* paths in the SecurePages configuration in the first place. Is there any strong reason for doing that?
Comment #3
Gábor HojtsyWell, I've removed /mollom/* from the securepages setup, and it was broken the same way, the audio was requested from http, so I cannot reproduce it using the same domain as you've explained.
Comment #4
easp CreditAttribution: easp commentedI ran into the same issue where I could not get the audio function to work with secure pages.
I added "mollom/*" to the ignore pages field within the secure pages settings. It fixed my issue.