Unsafe links to external sites

Hi Peter,

The SVG element namespace attribute does not use that for any communication, this is how they must be used, it is a w3tc definition. Omitting/changing the namespace will make them unusable.
The error is definitely triggered by something else.

Best,
Ernest M.

Hi Ernest
Thanks for the reply
But I do not agree with you
I checked the whole site for http only links.
Every page works well, but only if I use your search with the monocle it gives me the unsafe connection
I tried the example I gave you with https, and that works fine with https.
So I cannot imagine that thus organisation still prescribes unsafe links.
If it is not corrected I have to stop using your plugin. Which would be a pity as it is s nice plugin.
I already tested anither plugin, that does the same but without the unsafe warnings
Regards,
Peter

Hi,

Once again, this is not a request URL, but a namespace attribute. Please see XML namespaces, for SVG elements this namespace is defined here.

If there is an unsafe warning error, it is not caused by this, as it cannot be caused by this. Please see our demo site for example. It uses the same SVG elements, and there is no padlock issue, as this is how SVG elements are defined.

If you don’t see any other “http” requests in the source, then it is more likely caused by an asynchronous or XHR request, that is most likely initiated via javascript, and you won’t find by only looking at the source. Other causes can be .htaccess redirections, which are also invisible on the page source.

If you want, you can share your site URL, and I can take look at the requests, to see which might be causing the problem.

Best,
Ernest M.

Hi Ernest

I have been checking my system to see if a post has a wrong link. If I perform a search on bestuur (dutch) it shows the yellow sign. If I open the posts one by one the yellow sign disappears.
Please have a look at the following site “amandihuis.nl” or “hospiceamandi.nl”
Both sites have your plugin installed and are running with https
Thanks for investigating this
Peter

Hi Ernest

On the site “amandihuis.nl” it is now working properly
I have changed the following lines to “https”, and hopla the error is gone!

<div class=’innericon’>
<svg version=”1.1″ xmlns=”https://www.w3.org/2000/svg&#8221; xmlns:xlink=”https://www.w3.org/1999/xlink&#8221; x=”0px” y=”0px” width=”512px” height=”512px” viewBox=”0 0 512 512″ enable-background=”new 0 0 512 512″ xml:space=”preserve”>

I did that for every occurence I found
Regards,
Peter

Hi Peter,

Actually, id didn’t helps, as if I do a live search, the images returned are via non-secure protocols: https://i.imgur.com/x2uORia.png
The other site is also fine, until I do a single search and as soon as the search returns the results with the images requested, it fails.
These are requested from the WordPress core and served as-is, so there must be a configuration issue (site URL set as http etc..) – probably under the Settings -> General menu or similar. If the site URL was changed from HTTP to HTTPS at some point, then some other measures might be required.

Best,
Ernest M.

Hi Ernest

Thanks for your analyses. The behavior has improved after I altered your source to https
Previous it did it every time. Now as you indicated,after a single search.
All pages and posts do not produce this.
It is just the search that creates it.
The site has indeed been altered from http to https and produced the problem with images that have been added with a http link. But those errors are corrected, and now work fine.
I will read the docs you indicated, and see if I can do something with that.
Thanks