Title: CSS HTTPS mixed content issue
Last modified: June 12, 2018

---

# CSS HTTPS mixed content issue

 *  Resolved [wandererkh](https://wordpress.org/support/users/wandererkh/)
 * (@wandererkh)
 * [8 years ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/)
 * 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 [http://domain/wp-content/&#8230](http://domain/wp-content/&#8230);
   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](https://wordpress.org/support/users/dryabov/)
 * (@dryabov)
 * [8 years ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10392639)
 * 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](https://wordpress.org/support/users/wandererkh/)
 * (@wandererkh)
 * [8 years ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10395906)
 * 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](https://wordpress.org/support/users/dryabov/)
 * (@dryabov)
 * [7 years, 12 months ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10396010)
 * Just to be sure, what does style.css contain exactly: “url(/wp-content/…”, “url(
   wp-content/…”, or “url(images/…”?
 *  Plugin Author [Denis Ryabov](https://wordpress.org/support/users/dryabov/)
 * (@dryabov)
 * [7 years, 12 months ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10396214)
 * We have reproduced the issue. “Minify CSS Method: RESS” optimization works correctly,
   and others will be fixed in next release.
 *  Thread Starter [wandererkh](https://wordpress.org/support/users/wandererkh/)
 * (@wandererkh)
 * [7 years, 12 months ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10398882)
 * Thank you!
 *  Plugin Author [Denis Ryabov](https://wordpress.org/support/users/dryabov/)
 * (@dryabov)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10438946)
 * 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.

 * ![](https://ps.w.org/psn-pagespeed-ninja/assets/icon.svg?rev=1722219)
 * [PageSpeed Ninja - Cache, Minify, Defer CSS JavaScript, Critical CSS, Optimize Images, Convert WebP](https://wordpress.org/plugins/psn-pagespeed-ninja/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/psn-pagespeed-ninja/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/psn-pagespeed-ninja/)
 * [Active Topics](https://wordpress.org/support/plugin/psn-pagespeed-ninja/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/psn-pagespeed-ninja/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/psn-pagespeed-ninja/reviews/)

## Tags

 * [css](https://wordpress.org/support/topic-tag/css/)
 * [HTTPS](https://wordpress.org/support/topic-tag/https/)

 * 6 replies
 * 2 participants
 * Last reply from: [Denis Ryabov](https://wordpress.org/support/users/dryabov/)
 * Last activity: [7 years, 11 months ago](https://wordpress.org/support/topic/css-https-mixed-content-issue/#post-10438946)
 * Status: resolved