Re-enable storage for Suborigins.

content/common/origin_util_unittest.cc

Index: content/common/origin_util_unittest.cc
diff --git a/content/common/origin_util_unittest.cc b/content/common/origin_util_unittest.cc
index 3c2328bff9928f5f5812f8169c354a2424e89401..c7e5c99ab28eff015c52490db91a5f045cd8c97f 100644
--- a/content/common/origin_util_unittest.cc
+++ b/content/common/origin_util_unittest.cc
@@ -47,4 +47,18 @@ TEST(URLSchemesTest, IsOriginSecure) {
       IsOriginSecure(GURL("filesystem:https://www.example.com/temporary/")));
 }
 
+TEST(OriginUtilTest, Suborigins) {
+  GURL no_suborigin_url("https://example.com");
+  GURL suborigin_url("https-so://foobar.example.com");

[nasko, 2016/09/26 22:54:55]

Should "https-so://foo.com" succeed?

[jww, 2016/09/28 23:35:15]

Yes, it should. These are meant to be pure parsing mechanisms, effectively. As
long as its a valid URL, it will extract what would be the suborigin from it.

+
+  EXPECT_FALSE(HasSuborigin(no_suborigin_url));
+  EXPECT_TRUE(HasSuborigin(suborigin_url));
+
+  EXPECT_EQ("", SuboriginFromUrl(no_suborigin_url));
+  EXPECT_EQ("foobar", SuboriginFromUrl(suborigin_url));
+
+  EXPECT_EQ(no_suborigin_url, UrlStripSuborigin(no_suborigin_url));
+  EXPECT_EQ(no_suborigin_url, UrlStripSuborigin(suborigin_url));
+}

[nasko, 2016/09/26 22:54:55]

What about some negative test cases? "https-so://."?

[jww, 2016/09/28 23:35:15]

Done.

+
 }  // namespace content