• Resolved capsid

    (@capsid)


    Hello, I was having an insecure content warning (and thus no green lock) on my woocommerce checkout page. I traced this back to a link in an autoptimize cache file. I figure maybe I could exclude a certain CSS file from autoptimize to fix this but I’m unsure how to tell which file is offending. Do you have any insight on how to fix this kind of conflict with SSL and autoptimize?

    Debug info from whynopadlock
    http://imgur.com/7jaRdSf

    https://wordpress.org/plugins/autoptimize/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Frank Goossens

    (@futtta)

    hmmm … some questions;
    1. can you check your site on whynopadlock like this https://yoursite.com/checkout/?ao_noptimize=1 appended to the URL?
    2. is the insecure link a background image?
    3. is the insecure link on your own site, or does it point elsewhere?
    4. do you have “Generate data: URIs for images?” activated?
    5. do you have a CDN url configured in AO?

    frank

    Thread Starter capsid

    (@capsid)

    Hi Frank! 🙂

    1) I get the exact same result with that appended to the URL, same cache file and everything.

    2) I don’t believe so. The imgur link above shows it as being a link to the /shop/ page.

    3) The insecure link (the link to the shop page from within the cache file) is on our site, the same domain.

    4) I do NOT have “Generate data: URI’s for images” activated. Should I?

    5) I do NOT have a CDN URL configured but we are using a CDN. It’s configured to be part of our domain at cdn.ourdomain.com. Should I use that setting?

    Thanks for your help, let me know how I can proceed to help test.

    Plugin Author Frank Goossens

    (@futtta)

    hmmm … so that info didn’t help really, still no idea what is happening I’m afraid 🙂

    could you provide me with the autoptimize-file that has the insecure link or with the URL of your site (here or via futtta-at-gmail-dot-com) so I can stare the ssl-busting beast in the eye?

    frank

    Plugin Author Frank Goossens

    (@futtta)

    Update: the autoptimized-CSS file didn’t contain any reference to a HTTP-resource, and further investigation did not result in a clear root-cause for this pretty behavior (we concluded it was not impossible that the hoster’s SSL-configuration was somehow to blame).

    If anyone comes accross a similar problem; one can always disable AO on a per-URL basis using the autoptimize_filter_noptimize in the API as per the example in /wp-content/plugins/autoptimize/autopitmize_helper.php_example.

    frank

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Link in autoptimize cache causing insecure content warnings over SSL/’ is closed to new replies.