Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

https without a lock

  • 4 Antworten
  • 2 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von cor-el

more options

I went to a youtube site "https://www.youtube.com/watch?v=EASmyA6F29s" and the favicon shows https without a lock. I thought this should not occur in firefox 22 according to the documentation

Why is https being shown without a lock symbol as it clearly is not secure? See enclosed diagram.

I went to a youtube site "https://www.youtube.com/watch?v=EASmyA6F29s" and the favicon shows https without a lock. I thought this should not occur in firefox 22 according to the documentation Why is https being shown without a lock symbol as it clearly is not secure? See enclosed diagram.

Alle Antworten (4)

more options

What does this Https field represent without a lock symbol?

Geändert am von Mace2

more options

There is mixed content on that page.
Firefox only blocks active mixed content and if other mixed content like images are present then you still get the globe instead of the padlock.
You can see that in the Web Console (Firefox/Tools > Web Developer;Ctrl+Shift+K) as red lines.

more options

Thanks Cor-el

I understand that content is mixed. Is it possible to prevent any non https from being displayed or accepted? Because https has no meaning if a user cannot determine which content is secure.

more options

See:

There are these two pref that determine what content is blocked or passed

  • security.mixed_content.block_active_content (true)
  • security.mixed_content.block_display_content (false)