blocks|key|3159069|text|我遇到的一个解决方案是EdtFTPnet|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3159070|EdtFTPnet似乎是一个很有特色的解决方案，可以处理很多不同的FTP选项，所以非常理想。|3159071|这是我在http://www.ftp2rss.com上使用的免费开源解决方案(这是我自己需要的一个小工具，但我觉得可能对其他人也有用)。|3159072|entityMap|0|LINK|mutability|MUTABLE|url|http://www.enterprisedt.com/products/edtftpnet/documentation.html|1|http://www.ftp2rss.com/^0|B|9|0|0|0|4|M|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

One solution I came across is <a href="http://www.enterprisedt.com/products/edtftpnet/documentation.html" rel="nofollow">EdtFTPnet</a>

EdtFTPnet seems to be quite a feature packed solution that handles lots of different FTP options so is ideal.

It's the free open source solution that I've how employed for <a href="http://www.ftp2rss.com" rel="nofollow">http://www.ftp2rss.com</a> (a little tool I needed myself but figured might be useful to others also).

blocks|key|2945221|text|看看Ftp.dll+FTP+client吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2945222|它包括用于Windows、Unix和Netware平台上大多数FTP服务器的automatic+directory+listing+parser。|2945223|请注意，这是我开发的商业产品。|2945224|entityMap|0|LINK|mutability|MUTABLE|url|https://www.limilabs.com/ftp/|1|https://www.limilabs.com/blog/get-file-folder-info-using-ftp^0|2|I|0|0|12|Y|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Take a look at <a href="https://www.limilabs.com/ftp/" rel="nofollow">Ftp.dll FTP client</a>. 

It includes <a href="https://www.limilabs.com/blog/get-file-folder-info-using-ftp" rel="nofollow">automatic directory listing parser</a> for most FTP servers on Windows, Unix and Netware platforms.

Please note that this is a commercial product I developed.

blocks|key|255798|text|我也面临着同样的问题，并且使用正则表达式构建了一个简单的(尽管不是非常健壮的)解决方案，使用捕获组从每行中解析出相关信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|255799|public+static+Regex+FtpListDirectoryDetailsRegex+=+new+Regex(@".*(?<month>(Jan%7CFeb%7CMar%7CApr%7CMay%7CJun%7CJul%7CAug%7CSep%7COct%7CNov%7CDec))\s*(?<day>[0-9]*)\s*(?<yearTime>([0-9]%7C:)*)\s*(?<fileName>.*)",+RegexOptions.Compiled+%7C+RegexOptions.IgnoreCase);|code-block|syntax|javascript|255800|然后，您可以通过以下方式从捕获组中提取值：|255801|++++++++string+ftpResponse+=+"-r--r--r--+1+ftp+ftp++++++++++++++0+Nov+19+11:08+aaa.txt";
++++++++Match+match+=+FtpListDirectoryDetailsRegex.Match(ftpResponse);
++++++++string+month+=+match.Groups["month"].Value;
++++++++string+day+=+match.Groups["day"].Value;
++++++++string+yearTime+=+match.Groups["yearTime"].Value;
++++++++string+fileName+=+match.Groups["fileName"].Value;|255802|需要注意的事项有：|255803|255804|此选项仅适用于上述ftpResponse变量中所述格式的目录响应。在我的例子中，我很幸运每次只能访问相同的FTP服务器，所以响应格式不太可能改变。|unordered-list-item|offset|length|style|CODE|255805|+yearTime变量可以表示文件时间戳的年份或时间。您需要通过查找冒号:字符的实例来手动解析它，冒号:字符将指示此捕获组包含时间而不是年份|255806|255807|entityMap^0|0|0|0|0|0|0|9|B|0|1|8|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|15|8|@$Q|16|R|17|S|T]]|9|@]|A|$]]|$1|U|3|V|5|P|7|18|8|@$Q|19|R|1A|S|T]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Y|$]]

I'm facing this same problem and have built a simple (albeit not very robust) solution using a Regex to parse out the relevant information from each line using capture groups:

<pre><code>public static Regex FtpListDirectoryDetailsRegex = new Regex(@".*(?&lt;month&gt;(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec))\s*(?&lt;day&gt;[0-9]*)\s*(?&lt;yearTime&gt;([0-9]|:)*)\s*(?&lt;fileName&gt;.*)", RegexOptions.Compiled | RegexOptions.IgnoreCase);
</code></pre>

You can then extract the values out of the capture groups by:

<pre><code> string ftpResponse = "-r--r--r-- 1 ftp ftp 0 Nov 19 11:08 aaa.txt";
 Match match = FtpListDirectoryDetailsRegex.Match(ftpResponse);
 string month = match.Groups["month"].Value;
 string day = match.Groups["day"].Value;
 string yearTime = match.Groups["yearTime"].Value;
 string fileName = match.Groups["fileName"].Value;
</code></pre>

Some things not note are:

<ul>
<li>this will only work for directory responses with the format described found in the <code>ftpResponse</code> variable above. In my case I'm lucky to only be accessing the same FTP server each time and so it is unlikely that the response format will change.</li>
<li>the <code>yearTime</code> variable can represent EITHER the year or the time of the file's timestamp. You will need to parse this manually by looking for an instance of the colon : character which will indicate that this capture group contains a time rather than the year</li>
</ul>

blocks|key|261032|text|对于第一个(DOS/Windows)清单，此代码将执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|261033|FtpWebRequest+request+=+(FtpWebRequest)WebRequest.Create("ftp://ftp.example.com/");
request.Credentials+=+new+NetworkCredential("user",+"password");
request.Method+=+WebRequestMethods.Ftp.ListDirectoryDetails;
StreamReader+reader+=+new+StreamReader(request.GetResponse().GetResponseStream());

string+pattern+=+@"%5E(\d%2B-\d%2B-\d%2B\s%2B\d%2B:\d%2B(?:AM%7CPM))\s%2B(<DIR>%7C\d%2B)\s%2B(.%2B)$";
Regex+regex+=+new+Regex(pattern);
IFormatProvider+culture+=+CultureInfo.GetCultureInfo("en-us");
while+(!reader.EndOfStream)
{
++++string+line+=+reader.ReadLine();
++++Match+match+=+regex.Match(line);
++++string+s+=+match.Groups[1].Value;
++++DateTime+modified+=
++++++++DateTime.ParseExact(s,+"MM-dd-yy++hh:mmtt",+culture,+DateTimeStyles.None);
++++s+=+match.Groups[2].Value;
++++long+size+=+(s+!=+"<DIR>")+?+long.Parse(s)+:+0;
++++string+name+=+match.Groups[3].Value;

++++Console.WriteLine(
++++++++"{0,-16}+size+=+{1,9}++modified+=+{2}",
++++++++name,+size,+modified.ToString("yyyy-MM-dd+HH:mm"));
}|code-block|syntax|javascript|261034|您将获得：|261035|Version2+++++++++size+=+++++++++0++modified+=+2011-08-10+12:02
image34.gif++++++size+=+144700153++modified+=+2009-06-25+14:41
updates.txt++++++size+=+144700153++modified+=+2009-06-25+14:51
digger.tif+++++++size+=+144700214++modified+=+2010-11-04+14:45|261036|261037|有关其他(*nix)列表，请参见my+answer+to+Parsing+FtpWebRequest+ListDirectoryDetails+line。|offset|length|261038|261039|但是，实际上，尝试解析ListDirectoryDetails返回的列表并不是正确的方法。|style|CODE|261040|您希望使用支持现代MLSD命令的FTP客户端，该命令以RFC+3659中指定的机器可读格式返回目录列表。在与不支持LIST命令的过时FTP服务器(如Microsoft+IIS+FTP服务器)交谈时，应将解析由古老的FTP命令(由FtpWebRequest内部用于其ListDirectoryDetails方法)返回的人类可读格式用作最后的手段。|261041|261042|例如，对于WinSCP+.NET+assembly，您可以使用它的Session.ListDirectory或Session.EnumerateRemoteFiles方法。|261043|它们在内部使用MLSD命令，但可以退回到LIST命令，并支持数十种不同的人类可读的列表格式。|261044|返回的清单显示为具有以下属性的RemoteFileInfo+instances集合：|261045|261046|Name|unordered-list-item|261047|LastWriteTime+(具有正确的timezone)|261048|Length|261049|FilePermissions+(解析为单独的rights)|261050|Group|261051|Owner|261052|IsDirectory|261053|IsParentDirectory|261054|IsThisDirectory|261055|261056|(我是WinSCP的作者)|261057|261058|大多数其他第三方库也会做同样的事情。出于此目的，使用FtpWebRequest+class是不可靠的。不幸的是，在.NET框架中没有其他内置的FTP客户端。|261059|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/q/1013486/850848#40045894|1|https://datatracker.ietf.org/doc/html/rfc3659|2|https://winscp.net/eng/docs/library|3|https://winscp.net/eng/docs/library_session_listdirectory|4|https://winscp.net/eng/docs/library_session_enumerateremotefiles|5|https://winscp.net/eng/docs/library_remotefileinfo|6|https://docs.microsoft.com/en-us/dotnet/api/system.net.ftpwebrequest^0|0|0|0|0|0|G|1O|0|0|0|B|K|0|9|4|1L|4|36|D|3O|K|R|8|1|0|0|X|L|1J|S|5|K|2|X|L|3|1J|S|4|0|7|4|K|4|0|F|E|F|O|5|0|0|0|4|0|0|D|0|0|6|0|0|F|0|0|5|0|0|5|0|0|B|0|0|H|0|0|F|0|0|0|0|Q|D|Q|J|6|0^^$0|@$1|2|3|4|5|6|7|2D|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|2E|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|2F|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|2G|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|2I|8|@]|9|@$N|2J|O|2K|1|2L]]|A|$]]|$1|P|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2N|8|@$N|2O|O|2P|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|2Q|8|@$N|2R|O|2S|S|T]|$N|2T|O|2U|S|T]|$N|2V|O|2W|S|T]|$N|2X|O|2Y|S|T]]|9|@$N|2Z|O|30|1|31]]|A|$]]|$1|W|3|-4|5|6|7|32|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|33|8|@$N|34|O|35|S|T]|$N|36|O|37|S|T]]|9|@$N|38|O|39|1|3A]|$N|3B|O|3C|1|3D]|$N|3E|O|3F|1|3G]]|A|$]]|$1|Z|3|10|5|6|7|3H|8|@$N|3I|O|3J|S|T]|$N|3K|O|3L|S|T]]|9|@]|A|$]]|$1|11|3|12|5|6|7|3M|8|@$N|3N|O|3O|S|T]]|9|@$N|3P|O|3Q|1|3R]]|A|$]]|$1|13|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]|$1|14|3|15|5|16|7|3T|8|@$N|3U|O|3V|S|T]]|9|@]|A|$]]|$1|17|3|18|5|16|7|3W|8|@$N|3X|O|3Y|S|T]]|9|@]|A|$]]|$1|19|3|1A|5|16|7|3Z|8|@$N|40|O|41|S|T]]|9|@]|A|$]]|$1|1B|3|1C|5|16|7|42|8|@$N|43|O|44|S|T]]|9|@]|A|$]]|$1|1D|3|1E|5|16|7|45|8|@$N|46|O|47|S|T]]|9|@]|A|$]]|$1|1F|3|1G|5|16|7|48|8|@$N|49|O|4A|S|T]]|9|@]|A|$]]|$1|1H|3|1I|5|16|7|4B|8|@$N|4C|O|4D|S|T]]|9|@]|A|$]]|$1|1J|3|1K|5|16|7|4E|8|@$N|4F|O|4G|S|T]]|9|@]|A|$]]|$1|1L|3|1M|5|16|7|4H|8|@$N|4I|O|4J|S|T]]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|4K|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|4L|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|4M|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|4N|8|@$N|4O|O|4P|S|T]]|9|@$N|4Q|O|4R|1|4S]]|A|$]]|$1|1T|3|-4|5|6|7|4T|8|@]|9|@]|A|$]]]|1U|$1V|$5|1W|1X|1Y|A|$1Z|20]]|21|$5|1W|1X|1Y|A|$1Z|22]]|23|$5|1W|1X|1Y|A|$1Z|24]]|25|$5|1W|1X|1Y|A|$1Z|26]]|27|$5|1W|1X|1Y|A|$1Z|28]]|29|$5|1W|1X|1Y|A|$1Z|2A]]|2B|$5|1W|1X|1Y|A|$1Z|2C]]]]

For the first (DOS/Windows) listing this code will do:
<pre><code>FtpWebRequest request = (FtpWebRequest)WebRequest.Create(&quot;ftp://ftp.example.com/&quot;);
request.Credentials = new NetworkCredential(&quot;user&quot;, &quot;password&quot;);
request.Method = WebRequestMethods.Ftp.ListDirectoryDetails;
StreamReader reader = new StreamReader(request.GetResponse().GetResponseStream());

string pattern = @&quot;^(\d+-\d+-\d+\s+\d+:\d+(?:AM|PM))\s+(&lt;DIR&gt;|\d+)\s+(.+)$&quot;;
Regex regex = new Regex(pattern);
IFormatProvider culture = CultureInfo.GetCultureInfo(&quot;en-us&quot;);
while (!reader.EndOfStream)
{
 string line = reader.ReadLine();
 Match match = regex.Match(line);
 string s = match.Groups[1].Value;
 DateTime modified =
 DateTime.ParseExact(s, &quot;MM-dd-yy hh:mmtt&quot;, culture, DateTimeStyles.None);
 s = match.Groups[2].Value;
 long size = (s != &quot;&lt;DIR&gt;&quot;) ? long.Parse(s) : 0;
 string name = match.Groups[3].Value;

 Console.WriteLine(
 &quot;{0,-16} size = {1,9} modified = {2}&quot;,
 name, size, modified.ToString(&quot;yyyy-MM-dd HH:mm&quot;));
}
</code></pre>
You will get:
<pre class="lang-none prettyprint-override"><code>Version2 size = 0 modified = 2011-08-10 12:02
image34.gif size = 144700153 modified = 2009-06-25 14:41
updates.txt size = 144700153 modified = 2009-06-25 14:51
digger.tif size = 144700214 modified = 2010-11-04 14:45
</code></pre>
<hr />
For the other (*nix) listing, see <a href="https://stackoverflow.com/q/1013486/850848#40045894">my answer to Parsing FtpWebRequest ListDirectoryDetails line</a>.
<hr />
But, actually trying to parse the listing returned by the <code>ListDirectoryDetails</code> is not the right way to go.
You want to use an FTP client that supports the modern <code>MLSD</code> command that returns a directory listing in a machine-readable format specified in the <a href="https://datatracker.ietf.org/doc/html/rfc3659" rel="nofollow noreferrer">RFC 3659</a>. Parsing the human-readable format returned by the ancient <code>LIST</code> command (used internally by the <code>FtpWebRequest</code> for its <code>ListDirectoryDetails</code> method) should be used as the last resort option, when talking to obsolete FTP servers, that do not support the <code>MLSD</code> command (like the Microsoft IIS FTP server).
<hr />
For example with <a href="https://winscp.net/eng/docs/library" rel="nofollow noreferrer">WinSCP .NET assembly</a>, you can use its <a href="https://winscp.net/eng/docs/library_session_listdirectory" rel="nofollow noreferrer"><code>Session.ListDirectory</code></a> or <a href="https://winscp.net/eng/docs/library_session_enumerateremotefiles" rel="nofollow noreferrer"><code>Session.EnumerateRemoteFiles</code></a> methods.
They internally use the <code>MLSD</code> command, but can fall back to the <code>LIST</code> command and support dozens of different human-readable listing formats.
The returned listing is presented as collection of <a href="https://winscp.net/eng/docs/library_remotefileinfo" rel="nofollow noreferrer"><code>RemoteFileInfo</code> instances</a> with properties like:
<ul>
<li><code>Name</code></li>
<li><code>LastWriteTime</code> (with correct timezone)</li>
<li><code>Length</code></li>
<li><code>FilePermissions</code> (parsed into individual rights)</li>
<li><code>Group</code></li>
<li><code>Owner</code></li>
<li><code>IsDirectory</code></li>
<li><code>IsParentDirectory</code></li>
<li><code>IsThisDirectory</code></li>
</ul>
(I'm the author of WinSCP)
<hr />
Most other 3rd party libraries will do the same. Using the <a href="https://docs.microsoft.com/en-us/dotnet/api/system.net.ftpwebrequest" rel="nofollow noreferrer"><code>FtpWebRequest</code> class</a> is not reliable for this purpose. Unfortunately, there's no other built-in FTP client in the .NET framework.

I'm creating a service to monitor FTP locations for new updates and require the ability to parse the response returned from a FtpWebRequest response using the WebRequestMethods.Ftp.ListDirectoryDetails method. It would be fairly easy if all responses followed the same format, but different FTP server software provide different response formats.

For example one might return:

<pre><code>08-10-11 12:02PM &lt;DIR&gt; Version2
06-25-09 02:41PM 144700153 image34.gif
06-25-09 02:51PM 144700153 updates.txt
11-04-10 02:45PM 144700214 digger.tif
</code></pre>

And another server might return:

<pre><code>d--x--x--x 2 ftp ftp 4096 Mar 07 2002 bin
-rw-r--r-- 1 ftp ftp 659450 Jun 15 05:07 TEST.TXT
-rw-r--r-- 1 ftp ftp 101786380 Sep 08 2008 TEST03-05.TXT
drwxrwxr-x 2 ftp ftp 4096 May 06 12:24 dropoff
</code></pre>

And other differences have been observed also so there's likely to be a number of subtle differences I haven't encountered yet.

Does anyone know of a fully managed (doesn't require access to external dll on Windows) C# class that handles these situations seamlessly?

I only need to list the contents of a directory with the following details: File/directory name, last updated or created timestamp, file/directory name.

Thanks in advance for any suggestions,
Gavin

C# class to parse WebRequestMethods.Ftp.ListDirectoryDetails FTP response

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在创建一个服务来监视FTP位置是否有新的更新，并且需要能够使用WebRequestMethods.Ftp.ListDirectoryDetails方法解析从FtpWebRequest响应返回的响应。如果所有响应都遵循相同的格式，这将是相当容易的，但不同的FTP服务器软件提供不同的响应格式。例如，可以返回：08-10...

问用于解析WebRequestMethods.Ftp.ListDirectoryDetails FTP响应的C#类
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于解析WebRequestMethods.Ftp.ListDirectoryDetails FTP响应的C#类EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用于解析WebRequestMethods.Ftp.ListDirectoryDetails FTP响应的C#类
EN