Re-enable storage for Suborigins.

content/common/origin_util_unittest.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/public/common/origin_util.h"
 #include "testing/gtest/include/gtest/gtest.h"
 #include "url/gurl.h"
 
 namespace content {
 
@@ skipping 29 matching lines @@
 
   EXPECT_FALSE(
       IsOriginSecure(GURL("filesystem:http://www.example.com/temporary/")));
   EXPECT_FALSE(
       IsOriginSecure(GURL("filesystem:ftp://www.example.com/temporary/")));
   EXPECT_TRUE(IsOriginSecure(GURL("filesystem:ftp://127.0.0.1/temporary/")));
   EXPECT_TRUE(
       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