Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

How to identify insecure elements in my site https://historyradio.org/

  • 2 svar
  • 1 har detta problem
  • 1 visning
  • Senaste svar av michaelwy

more options

I have an educational website at https://historyradio.org/ . I try to keep it in working condition. It is listed as safe by all other browsers than firefox. In firefox, i get a message saying that some elements (images) are "insecure". But how can image files be insecure, and how can I as a webmaster identify which images and which elements that are insecure so that I can fix the problem?

I have an educational website at https://historyradio.org/ . I try to keep it in working condition. It is listed as safe by all other browsers than firefox. In firefox, i get a message saying that some elements (images) are "insecure". But how can image files be insecure, and how can I as a webmaster identify which images and which elements that are insecure so that I can fix the problem?

Vald lösning

Go to ≡ → Web Developer → Network and refresh your page.

Läs svaret i sitt sammanhang 👍 1

Alla svar (2)

more options

Vald lösning

Go to ≡ → Web Developer → Network and refresh your page.

more options

That was very useful thanks. While I cannot see that any of my images come up as insecure; i can see that some are hosted on facebook, an external site. This is part of the facebook like box app. This must be the cause of my insecure site warning. However, there is nothing i can do about it. I need the facebook like box. But at least, now I have identified the issue. Thanks.