Like someone that wrote earlier, I got an error from ahrefs. More exactly: Non-canonical page in sitemap, that relates to the sitemap generated by yoast. In the sitemap I have http, not https.

How can I change this?

I was able to install WordPress stand alone on my server and turned subdomain to true. I also sat SSL supposed to be for wildcard and domain.com.
now if I open my site, I only can open default site as domain.com, if I add www, it takes me to the initial Apache / Fedora page… I been working on this for almost three weeks and frustrated as a lot of Garbage information on the Net. The other issue when I’m logged in wp-admin main site and want switch to the subdomain site .. it takes me to https://subdomain.domain.com and the page shows not found. If I remove the s from https, then I can go to it and edit and work find. … if I want visit the site I have also to go to http and not https even the wildcard is installed from letsencrypt. I have looked at httpd.conf, wp-conf.php, .htaccess and lots more including white pages, crashes .. just to get the problem resolve and I’m going in circles .. I hope that someone can help me here and will be much appreciated !

Very nice plugin. Thanks!

We have a blog website which uses blocksy theme and hosted on a server and it is connected to a separate server(plasticheroglobal.com) through nginx configuration as a /blog/ directory. The website is working, and in our general settings below are the URLs that we configured

WordPress Address (URL) :- https://internal-admin2024.plasticheroglobal.com

Site Address (URL) :- https://plasticheroglobal.com/blog

The website is loading but with mixed content errors on the console. We checked over the source and every file of the theme and we are not able to find anything on https://, everything is loading on SSL(https://), However the console shows mixed content errors. PFA. Is there any way to fix this issue?

screenshot :- https://tinyurl.com/24jlmfzy

Please check and let us know your feedback

Thank you

I am trying to modify http headers with your plugin.

So, I have created a simple snippet which do this:

add_filter('wp_headers', 'my_custom_headers');

function my_custom_headers($headers) {
	// Add X-XSS-Protection header
	if (!isset($headers['X-XSS-Protection'])) {
		$headers['X-XSS-Protection'] = '1; mode=block;';
	}

	// Add X-Content-Type-Options header
	if (!isset($headers['X-Content-Type-Options'])) {
		$headers['X-Content-Type-Options'] = 'nosniff';
	}

	return $headers;
}

But, $headers variables only contain “Content-Type” value.

In fact I would like to be able to check if headers have already being sent (from .htaccess by example) and be able to modify them.

So, what is the way to get http headers in order to control them with WPCode snippet?

Thanks in advance for your help and have a nice day.

I wanted to know if it was possible to remove HTTP headers easily?

For example, I would like to remove the header named “X-Powered-By”

It would be really nice if we could make it as easy as adding more.

Thank you in advance for your help and I wish you a pleasant day.

Mixed Content: The page at 'https://karamaria.com/works-on-paper/' was loaded over HTTPS, but requested an insecure stylesheet 'https://karamaria.com/wp-content/plugins/foogallery/extensions/default-templates/shared/css/foogallery.min.css?ver=2.4.16'. This request has been blocked; the content must be served over HTTPS.

and in a series of included plugin css files FooGallery is the only one that’s http:

<link rel='stylesheet' id='contact-form-7-css'  type='text/css' media='all' />
<link rel='stylesheet' id='foobox-free-min-css'  type='text/css' media='all' />
<link rel='stylesheet' id='foogallery-core-css'  type='text/css' media='all' />
<link rel='stylesheet' id='thumbs_rating_styles-css'  type='text/css' media='all' />
<link rel='stylesheet' id='sbtt-style-css'  type='text/css' media='all' />

I don’t know what generates that list but is it possible this is a bug in version 2.4.16?

To improve clarity and better align with HTTP status code conventions, I propose the following changes:

1. Use HTTP 429 Too Many Requests for Rate Limiting:
   • HTTP 429 is specifically designed to indicate that the user has sent too many requests in a given amount of time and should reduce the rate of requests. This status code would provide a clearer indication of rate limiting events.
2. Use HTTP 403 Forbidden for Permanent Blocks:
   • HTTP 403 indicates that the server understands the request but refuses to authorize it. This status code is well-suited for permanent blocks, clearly conveying that access is denied.