UPDATE - errors were generating from something else, httpsreplace script ran fine on our 3.2 version and provided a report of problematic domains. Now to test the fix!!
Security and privacy
Moving to HTTPS everywhere
This discussion has been locked because a year has elapsed since the last post. Please start a new discussion topic.