path: root/content/content.h
diff options
authorDaniel Silverstone <>2019-12-01 15:49:08 +0000
committerDaniel Silverstone <>2019-12-01 15:49:08 +0000
commit6fc2666d07f28cd845b5697853b9b0e61f8848c5 (patch)
tree441933bf0787bba0143c702dd25baf78a14925f7 /content/content.h
parent9741df214d7b291c8de40e9b21d4411e523d0bb3 (diff)
Allow contents to indicate if they believe they may not be secure.
HTML contents reference many other objects. The browser window needs to know if any of them may not be secure, in which case it needs to report that in its page state. If other content types might refer to sub-contents, they will need to define the callback too. Signed-off-by: Daniel Silverstone <>
Diffstat (limited to 'content/content.h')
1 files changed, 12 insertions, 0 deletions
diff --git a/content/content.h b/content/content.h
index f3e578b6b..0dbd58d95 100644
--- a/content/content.h
+++ b/content/content.h
@@ -420,5 +420,17 @@ bool content_is_locked(struct hlcache_handle *h);
bool content_exec(struct hlcache_handle *h, const char *src, size_t srclen);
+ * Determine if the content referred to any insecure objects.
+ *
+ * Query the content to determine if any of its referred objects were loaded
+ * in a manner not considered secure. For a content to be recursively
+ * secure it must only load over https and must not have certificate overrides
+ * in place.
+ *
+ * \param h The handle to the content
+ * \return Whether the content referred to any insecure objects
+ */
+bool content_saw_insecure_objects(struct hlcache_handle *h);