Clean up FTPNetworkTransaction to match the latest trace

net/ftp/ftp_network_transaction_unittest.cc

Index: net/ftp/ftp_network_transaction_unittest.cc
diff --git a/net/ftp/ftp_network_transaction_unittest.cc b/net/ftp/ftp_network_transaction_unittest.cc
index ede22d31b38f00585b66e262da7d6bc0fe536eac..79e16877bdd19d4ddd214cd66c288a1b415c46e0 100644
--- a/net/ftp/ftp_network_transaction_unittest.cc
+++ b/net/ftp/ftp_network_transaction_unittest.cc
@@ -918,7 +918,7 @@ TEST_P(FtpNetworkTransactionTest, DirectoryTransactionWithPasvFallback) {
 
 TEST_P(FtpNetworkTransactionTest, DirectoryTransactionWithTypecode) {
   FtpSocketDataProviderDirectoryListing ctrl_socket;
-  ExecuteTransaction(&ctrl_socket, "ftp://host;type=d", OK);
+  ExecuteTransaction(&ctrl_socket, "ftp://host/;type=d", OK);

[xunjieli, 2015/01/30 21:50:44]

Added a "/" here so that ";type=d" will not be interpreted as a part of the
host. It seems there should be a slash according to RFC 1738 section 3.2.2.

type=i and type=a are tested in DownloadTransactionWithTypecodeI and
DownloadTransactionWithTypecodeA.

[davidben, 2015/02/04 18:51:18]

Hah. Did this test just never actually test the type=d case before?

[xunjieli, 2015/02/04 20:29:29]

Yep. It was not tested before since "host;type=d" cannot be correctly parsed.

 
   EXPECT_TRUE(transaction_.GetResponseInfo()->is_directory_listing);
   EXPECT_EQ(-1, transaction_.GetResponseInfo()->expected_content_size);