Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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

  • 2 отговора
  • 1 има този проблем
  • 1 изглед
  • Последен отговор от 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?

Избрано решение

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

Прочетете този отговор в контекста 👍 1

Всички отговори (2)

more options

Избрано решение

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.