Avatar for Username

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Kjo rrjedhë është arkivuar. Ju lutemi, bëni një pyetje të re, nëse keni nevojë për ndihmë.

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

  • 2 përgjigje
  • 1 e ka hasur këtë problem
  • 1 parje
  • Përgjigjja më e re nga michaelwy

michaelwy
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?

Zgjidhje e zgjedhur

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

Lexojeni këtë përgjigje brenda kontekstit 👍 1

Krejt Përgjigjet (2)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Zgjidhja e Zgjedhur

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

michaelwy
michaelwy I zoti i pyetjes
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.