Correctly construct ("file", "", 0) SecurityOrigins.

Source/platform/weborigin/SecurityOriginTest.cpp

 /*
  * Copyright (C) 2013 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 344 matching lines @@
         {444, 444, "https://example.com:444"},
     };
 
     for (const auto& test : cases) {
         RefPtr<SecurityOrigin> origin = SecurityOrigin::createFromString(test.origin);
         EXPECT_EQ(test.port, origin->port());
         EXPECT_EQ(test.effectivePort, origin->effectivePort());
     }
 }
 
+TEST_F(SecurityOriginTest, CreateFromTuple)
+{
+    struct TestCase {
+        const char* scheme;
+        const char* host;
+        unsigned short port;
+        const char* origin;
+    } cases[] = {
+        {"http", "example.com", 80, "http://example.com"},
+        {"http", "example.com", 81, "http://example.com:81"},
+        {"https", "example.com", 443, "https://example.com"},
+        {"https", "example.com", 444, "https://example.com:444"},
+        {"file", "", 0, "file://"},
+        {"file", "example.com", 0, "file://"},

[jochen (gone - plz use gerrit), 2015/07/31 08:15:01]

Hm, file: can have a host, no?

[Mike West, 2015/07/31 15:21:27]

Yup. We serialize every `file:` URL as `file://` at the moment. Changing it to
include the host is probably a good idea, but that's not our current behavior.

+    };
+
+    for (const auto& test : cases) {
+        RefPtr<SecurityOrigin> origin = SecurityOrigin::create(test.scheme, test.host, test.port);
+        EXPECT_EQ(test.origin, origin->toString()) << test.origin;
+    }
+
+}
+
 } // namespace blink