DataReductionProxy proto change to use exp=force_lite_page directive

components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h

Index: components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h
diff --git a/components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h b/components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h
index 360914e06ad1d029edd651d4d3c2ff997dcaecc3..458f4861794abe76fb18bcbee09c21597df9fba8 100644
--- a/components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h
+++ b/components/data_reduction_proxy/core/common/data_reduction_proxy_headers.h
@@ -99,8 +99,8 @@ const char* identity_directive();
 const char* chrome_proxy_lite_page_directive();
 
 // Gets the Chrome-Proxy directive used by data reduction proxy lite page
-// preview experiment to ignore the blacklist.
-const char* chrome_proxy_lite_page_ignore_blacklist_directive();
+// preview experiment to force a lite page preview.

[megjablon, 2017/05/23 00:19:07]

Should we be more descriptive about what this does? "Forcing a lite page gets a
lite page, if it can be transcoded, regardless of the server blacklist and the
network quality". Or we can keep this opaque intentionally so that we can adapt
the meaning via the server as need be.

[dougarnett, 2017/05/23 17:02:17]

Actually had feedback from Ben for the sense of the latter (from my earlier
mondo CL).

+const char* chrome_proxy_force_lite_page_directive();
 
 // Requests a transformation only if the server determines that the page is
 // otherwise heavy (i.e., the associated page load ordinarily requires the