Allow paths constructed from URLs rather as well as cookie attributes.

net/cookies/canonical_cookie_unittest.cc

Index: net/cookies/canonical_cookie_unittest.cc
diff --git a/net/cookies/canonical_cookie_unittest.cc b/net/cookies/canonical_cookie_unittest.cc
index a2f3cf720231618598ab8d394370f44155915246..50c95d8048ae8acb8ca74302a099555c5b0c6970 100644
--- a/net/cookies/canonical_cookie_unittest.cc
+++ b/net/cookies/canonical_cookie_unittest.cc
@@ -44,14 +44,26 @@ TEST(CanonicalCookieTest, Constructor) {
   EXPECT_EQ(CookieSameSite::NO_RESTRICTION, cookie2->SameSite());
 }
 
-TEST(CanonicalCookie, SpaceInName) {
-  GURL url("http://www.example.com/test/foo.html");
+TEST(CanonicalCookie, CreationCornerCases) {
   base::Time creation_time = base::Time::Now();
   CookieOptions options;
-  std::unique_ptr<CanonicalCookie> cookie(
-      CanonicalCookie::Create(url, "A C=2", creation_time, options));
+  std::unique_ptr<CanonicalCookie> cookie;
+
+  // Space in name.
+  cookie = CanonicalCookie::Create(GURL("http://www.example.com/test/foo.html"),
+                                   "A C=2", creation_time, options);
   EXPECT_TRUE(cookie.get());
   EXPECT_EQ("A C", cookie->Name());
+
+  // Semicolon in path.
+  cookie = CanonicalCookie::Create(GURL("http://fool/;/"), "*", creation_time,
+                                   options);
+  EXPECT_TRUE(cookie.get());
+
+  // Space in path.
+  cookie = CanonicalCookie::Create(GURL("http://fool/xyzzy wwwww/"), "A=B",

[mmenke, 2017/06/28 00:26:20]

Doesn't GURL precent-escape spaces in paths?

[Randy Smith (Not in Mondays), 2017/06/28 14:58:05]

Yeah, it does :-J.  Ok.  What I think that means in terms of restrictions:
* A cookie attribute value can create a value with a space (not that this makes
sense for the reason you mention, but it could be done), but not a space at the
beginning or end.
* A path created from a URL will not have a space in it period.

So I think the canonical test should be "no space at beginning or end, but
spaces in middle allowed" with positive and negative tests as appropriate in
CreationCornerCases and IsCanonical.  SGTY?

[mmenke, 2017/06/28 17:13:48]

I'm wondering if it's worth the effort - I don't think there's a security issue
with paths that can never actually be matched?  There may also be weird
restrictions (Other characters that can't be in values, and are percent-escaped
in URLs).

[Randy Smith (Not in Mondays), 2017/06/28 17:41:21]

Sure.  My goal at the moment is just to get the fuzzer to shut up.  So combining
your response and that goal: I'll just remove the check against cookie value
parsing for path from the IsCanonical check?

+                                   creation_time, options);
+  EXPECT_TRUE(cookie.get());
 }
 
 TEST(CanonicalCookieTest, Create) {
@@ -742,20 +754,6 @@ TEST(CanonicalCookieTest, IsCanonical) {
                                COOKIE_PRIORITY_LOW)
                    .IsCanonical());
 
-  // Path suffixed with a space.
-  EXPECT_FALSE(CanonicalCookie("A", "B", "x.y", "/path ", base::Time(),
-                               base::Time(), base::Time(), false, false,
-                               CookieSameSite::NO_RESTRICTION,
-                               COOKIE_PRIORITY_LOW)
-                   .IsCanonical());
-
-  // Path suffixed with separator.
-  EXPECT_FALSE(CanonicalCookie("A", "B", "x.y", "/path;", base::Time(),
-                               base::Time(), base::Time(), false, false,
-                               CookieSameSite::NO_RESTRICTION,
-                               COOKIE_PRIORITY_LOW)
-                   .IsCanonical());
-
   // Simple IPv4 address as domain.
   EXPECT_TRUE(CanonicalCookie("A", "B", "1.2.3.4", "/path", base::Time(),
                               base::Time(), base::Time(), false, false,