
Problem is, the content, more precisely the image, isn't loaded using the protocol my server uses. So under HTTPS, this creates these warnings:


I would be interesting to fix the problem, so future navigation doesn't create these warnings.
Thanks!
David
