Allow huge data: URIs only via WebView.loadDataWithBaseUrl

content/common/navigation_params.h

Index: content/common/navigation_params.h
diff --git a/content/common/navigation_params.h b/content/common/navigation_params.h
index d4f88dc6c9951d895a980d8db6e985493b340967..5e5309020a040882998c889bc5321585790553e3 100644
--- a/content/common/navigation_params.h
+++ b/content/common/navigation_params.h
@@ -17,10 +17,6 @@
 #include "ui/base/page_transition_types.h"
 #include "url/gurl.h"
 
-namespace base {
-class RefCountedMemory;
-}
-
 namespace content {
 
 // The LoFi state which determines whether to add the Lo-Fi header.
@@ -60,6 +56,7 @@ struct CONTENT_EXPORT CommonNavigationParams {
                          FrameMsg_UILoadMetricsReportType::Value report_type,
                          const GURL& base_url_for_data_url,
                          const GURL& history_url_for_data_url,
+                         const std::string& data_url_as_string,
                          LoFiState lofi_state,
                          const base::TimeTicks& navigation_start);
   ~CommonNavigationParams();
@@ -105,6 +102,11 @@ struct CONTENT_EXPORT CommonNavigationParams {
   // Is only used with data: URLs.
   GURL history_url_for_data_url;
 
+  // The real content of the data: URL. Used to circumvent the restriction
+  // on the GURL max length. Note that it may only be passed from browser
+  // to renderer, not vice versa.

[boliu, 2015/12/09 19:33:02]

(only read up to this point) how is renderer->browser avoided?

(after finish reading everything) Sounds like a soft guarantee. Is everything
renderer->browser constructed from MakeCommonNavigationParams in
render_frame_impl.cc?

+  std::string data_url_as_string;
+
   // Whether or not to request a LoFi version of the document or let the browser
   // decide.
   LoFiState lofi_state;