Enable support for Rice encoding

components/safe_browsing_db/v4_update_protocol_manager.cc

Index: components/safe_browsing_db/v4_update_protocol_manager.cc
diff --git a/components/safe_browsing_db/v4_update_protocol_manager.cc b/components/safe_browsing_db/v4_update_protocol_manager.cc
index ab2142f6a61343701b58fbfbb4a2dbed6d8f5e62..ac84653bed1cc71ce8d02d84c994948890f4047a 100644
--- a/components/safe_browsing_db/v4_update_protocol_manager.cc
+++ b/components/safe_browsing_db/v4_update_protocol_manager.cc
@@ -215,6 +215,8 @@ std::string V4UpdateProtocolManager::GetBase64SerializedUpdateRequestProto(
     // TODO(vakh): Accept other compression formats also.

[Nathan Parker, 2016/08/19 00:18:22]

remove todo

[vakh (use Gerrit instead), 2016/08/19 00:46:35]

Done.

     // See: https://bugs.chromium.org/p/chromium/issues/detail?id=624567
     list_update_request->mutable_constraints()->add_supported_compressions(RAW);
+    list_update_request->mutable_constraints()->add_supported_compressions(

[Nathan Parker, 2016/08/19 00:18:22]

Are there any tests that is affects or should affect?  We might want to verify
we're requesting the expected list of threat types, among others.

[vakh (use Gerrit instead), 2016/08/19 00:46:35]

Good catch. Done.

+        RICE);
   }
 
   // Serialize and Base64 encode.