Bug 142340 - Insecure content warnings not emitted when favicon is restored from favicon cache?
Summary: Insecure content warnings not emitted when favicon is restored from favicon c...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 140625
  Show dependency tree / graph
 
Reported: 2015-03-05 06:42 PST by Michael Catanzaro
Modified: 2022-07-19 14:59 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2015-03-05 06:42:44 PST 
Sometimes I get insecure content warnings for the favicon on *.gnome.org. Sometimes I don't. I haven't investigated yet but a reasonable guess is that the favicon is checked to be mixed content only when first downloaded, and the result is never stored to be used on subsequent loads from the cache, similar to bug #138127.
Comment 1 Michael Catanzaro 2022-07-19 14:59:31 PDT 
If we fix bug #219396, then we can close this issue as obsolete because the favicon cache should never contain insecure content.