-
Notifications
You must be signed in to change notification settings - Fork 801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom CSS doesn't respect https #420
Comments
At least in the instance where I saw the issue, the scheme wasn't getting detected properly in Perhaps it could be set explicitly? |
Would something like this help? $prot = is_ssl() ? 'https' : 'http';
$href = home_url( '/', $prot ); |
Yeah I think that would work, give me a few minutes and I can test it to confirm. |
Hmm, interestingly, even setting the schema to |
I just tested it on a test site of mine, and setting the schema to Does your site use a reverse proxy, or anything that may force the use of |
@jeherve Please don't use a ternary with is_ssl -- instead use either |
Removing the schema complete would work fine. |
👍 . I didn't know about |
@pippinsplugins Did you test that? There's the chance that something in core would add a url scheme via |
Just to pipe in, I use custom css on my https only site without any issues. See https://store.halfelf.org/ for it. No invalid SSL :) |
Setting the scheme did not work, but removing the call to
|
Closing as "worksforme". |
Fixes #45 If a custom post type has no rewrite permalink then the plugin will clear the entire cache in wp_cache_post_id_gc() because get_current_url_supercache_dir() will strip the ?x=y from the URL, resulting in the URL being the homepage. The plugin then deletes everything below that. See also Automattic/wp-super-cache#66
I haven't dug into this yet, but it seems that the custom CSS module does not properly respect pages that are loaded on https and load the custom CSS file over http, resulting in SSL invalidation.
The text was updated successfully, but these errors were encountered: