1

Topic: .net + ListDirectoryDetails

Hello. There is a code: var webRequest = (FtpWebRequest) WebRequest. Create (uri); webRequest. Method = WebRequestMethods.Ftp.ListDirectoryDetails; Let uri there will be ftp://127.0.0.1/sta1, a result - inf-ija about a folder sta1, rather than about contents. Let uri there will be ftp://127.0.0.1/sta1/, a result - inf-ija about files in a folder sta1, i.e. that that is necessary. Why so? I.e. for ftp "ftp://127.0.0.1/sta1" is a file, and "ftp://127.0.0.1/sta1/" is already a folder? At once I will make a reservation that it was tested here with this operetta ftp the server that does not potter with "monsters".

2

Re: .net + ListDirectoryDetails

Hello, Sharov, you wrote: S> Hello. S> There is a code: S> S> var webRequest = (FtpWebRequest) WebRequest. Create (uri); S> webRequest. Method = WebRequestMethods.Ftp.ListDirectoryDetails; S> S> Let uri there will be ftp://127.0.0.1/sta1, a result - inf-ija about a folder sta1, rather than about contents. Let uri there will be ftp://127.0.0.1/sta1/, a result - inf-ija about files in a folder sta1, i.e. that that is necessary. S> Why so? I.e. for ftp "ftp://127.0.0.1/sta1" is a file, and "ftp://127.0.0.1/sta1/" is already a folder? S> at once I will make a reservation that it was tested here with this operetta ftp the server that does not potter with "monsters". A release. Checked up on "adults" ftp servers - differences any. It, probably, specificity given operetta ftp servers. Though the browser at request ftp://127.0.0.1/sta1  adds / in the end, i.e. is visible ftp://127.0.0.1/sta1 / more reliably.

3

Re: .net + ListDirectoryDetails

Hello, Sharov, you wrote: S> the Release. Checked up on "adults" ftp servers - differences any. It, probably, specificity given operetta ftp servers. Though the browser at request ftp://127.0.0.1/sta1  adds / in the end, i.e. is visible ftp://127.0.0.1/sta1 / more reliably. FTP as the protocol with numerous implementations - all a continuous operetta. The such forerunner of modern cross-browser JS hell. Migrate on HTTP (if probably). P.S. By the way, and why not IIS services? In the same place too FTP is, in the form of services is and on normal Windows (it is simple  through the Control bar).

4

Re: .net + ListDirectoryDetails

Hello, Mr. Delphist, you wrote: MD> Hello, Sharov, you wrote: S>> the Release. Checked up on "adults" ftp servers - differences any. It, probably, specificity given operetta ftp servers. Though the browser at request ftp://127.0.0.1/sta1  adds / in the end, i.e. is visible ftp://127.0.0.1/sta1 / more reliably. MD> FTP as the protocol with numerous implementations - all a continuous operetta. The such forerunner of modern cross-browser JS hell. Migrate on HTTP (if probably). MD> P.S. By the way, and why not IIS services? In the same place too FTP is, in the form of services is and on normal Windows (it is simple  through the Control bar). Yes, about built in ftp I know, but I for integration tests should create arbitrary (while 3) kol-in ftp servers with different daddies. Advantage of this operetta server that its is simply separate process in which parameters . A folder and port. Launched tests, lifted . Process with parameters, ran tests, beat process. All controllably also works as it is necessary. Another matter that without / it as a file understands in the end a folder. But it is removable.