HTTP code in the CDATA

I have been trying to lock down the last of the “http” code on my page.

I have found that there are two links that are generated under the CDATA that have hard http: links in them.

Two instances of this:
http:\/\/nginx.org\/en\/docs\/http\/ngx_http_autoindex_module.html

This is interfering with the https: loading of the website.

Not only is this interfering with the way the site works, it also breaks normal “best practice” for url links. The best practice has been for years to use https: for hard links or better yet, to simply use “//”.

Unfortunately, I haven’t been able to find anywhere within the code that actually references this.

On another thread, it describes this as an issue with the I18n handling and is related to a huge amount of code bloat for no apparent reason.

That thread was closed over two months ago and someone else pointed out that the http issue is a much bigger problem.

Neither of these has been addressed, but I see that you have continued updating this plugin.

I can live with a little bloat, but I cannot live with http: unsecure hard links in my page source.

This needs to be fixed 2 months ago. I would consider this very high priority since it affects the secure/unsecure status of all sites that use this plugin and in turn will also be affecting their Google ranking. I have had people messaging my clients telling them that their site is not secure simply because I am using your plugin. This is 100% unacceptable.

I did not build this plugin, but it took me less than half an hour to find the source of the problem. I am sure that the people who are involved in dev for this plugin should be able to fix this problem within just a few minutes.

Please get this dealt with. The HTTP/HTTPS standard issue has been a problem for a long time and just because it works fine in Chrome, it does not mean that all browsers have the same sensitivity level.

Please care for your code responsibly.