• Resolved wandererkh

    (@wandererkh)


    Hi,

    I’ve faced with new issue with HTTPS and caching: mixed content error in CSS url().
    Original css has relative URLs starting with /wp-content/ . Merged URL sometimes (when page is loaded over HTTP?) can have https://domain/wp-content/… URLs, be cached and loaded over HTTPS.
    Is it possible to have URLs without protocol type (starting with //) ?

    Thanks in advance

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Denis Ryabov

    (@dryabov)

    Hmm, PageSpeed Ninja shouldn’t append domain name to URLs in CSS, after merging they should be converted to links that start from the root of website (i.e. “/wp-content/…”). I’ll try to reproduce and fix it soon. Could you give URL of source file, part of source file with url(), and which CSS optimization method do you use?

    Thread Starter wandererkh

    (@wandererkh)

    css:
    /wp-content/themes/theme_name/style.css

    css part:
    .logo a{

    background: url(/wp-content/themes/theme_name/images/logo.png) 50% no-repeat;
    ..
    }

    Minify CSS Method: RESS + CSSTidy, changing doesn’t affect on issue
    Cross-files optimization: on, switching off doesn’t affect on issue
    Merge CSS files: on, switching off solves the problem

    Plugin Author Denis Ryabov

    (@dryabov)

    Just to be sure, what does style.css contain exactly: “url(/wp-content/…”, “url(wp-content/…”, or “url(images/…”?

    Plugin Author Denis Ryabov

    (@dryabov)

    We have reproduced the issue. “Minify CSS Method: RESS” optimization works correctly, and others will be fixed in next release.

    Thread Starter wandererkh

    (@wandererkh)

    Thank you!

    Plugin Author Denis Ryabov

    (@dryabov)

    Fixed in 0.9.27

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘CSS HTTPS mixed content issue’ is closed to new replies.