Fix our handling of mixed SSL / non-SSL content....

webkit/glue/webview_delegate.h

Index: webkit/glue/webview_delegate.h
===================================================================
--- webkit/glue/webview_delegate.h	(revision 11701)
+++ webkit/glue/webview_delegate.h	(working copy)
@@ -345,10 +345,13 @@
   // This method is called when we load a resource from an in-memory cache.
   // A return value of |false| indicates the load should proceed, but WebCore
   // appears to largely ignore the return value.
-  virtual bool DidLoadResourceFromMemoryCache(WebView* webview,
-                                              const WebRequest& request,
-                                              const WebResponse& response,
-                                              WebFrame* frame) {
+  virtual bool DidLoadResourceFromMemoryCache(
+      WebView* webview,
+      const WebRequest& request,
+      const WebResponse& response,
+      WebFrame* frame,
+      const std::string& frame_origin,

[jcampan, 2009/03/16 18:43:54]

Would it make sense to make the frame origins gettable from the WebResponse
(like we do with the security info)? That way these params would not have to be
passed around in method calls  that take a WebResponse.

[abarth-chromium, 2009/03/16 21:34:21]

I'm not sure that makes sense.  It's not really a property of the response. 
It's a property of the context that's receiving the response.  Maybe we should
add it to WebFrame?

+      const std::string& main_frame_origin) {
     return false;
   }