RE: ftp: mget specifying path names -- MIDRANGE-L

Yes, I didn't quote the part that would make it ambiguous. :)
--
Sean Porterfield

-----Original Message-----
From: Tim Brown
Sent: Thursday, January 31, 2013 11:02
To: Midrange Systems Technical Discussion
Subject: Re: ftp: mget specifying path names

Yes, that's exactly the point. If the server provides the name (regardless of the format) it HAS to understand now to reference that name. No ambiguity there.

On Thu, Jan 31, 2013 at 4:57 PM, Porterfield, Sean < SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I can see the ambiguity but reject it based on the end of the paragraph:

RFC959 NLST
"This command is intended to return information that can be used by a
program to further process the files automatically. For example, in
the implementation of a 'multiple get' function."
--
Sean Porterfield

-----Original Message-----
From: Rob Berendt
Sent: Thursday, January 31, 2013 10:50
Subject: Re: ftp: mget specifying path names

Thank you. But is that really that clear in the RFCs? If so, I can
run that by the vendor.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Tim Brown <tim.bronski@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/31/2013 08:37 AM
Subject: Re: ftp: mget specifying path names
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Hi Rob, as you probably know from looking at ftp logs a client MGET
command is actually an NLST followed followed by a get (RETR) for each
of the returned list entries. It's standard for a list that requests a
relative path to return the list with just the files names. In your
case however it's irrelevant. A server should be able to consume the
results of its own list. So if your server is responding to an NLST
with just file names then it MUST be able to retrieve (GET) a file
based on that same output.
Anything else doesn't make sense.So if the RETR uses the same values
that are on the NLST response then the server has a bug.

On Wed, Jan 30, 2013 at 11:12 PM, <rob@xxxxxxxxx> wrote:

When doing ftp make it a bad habit to do
mget /mypathname/*.*
versus
cd /mypathname
mget *.*
The reason being is that some servers will support the mget
/mypathname/*.* and others won't.
I've seen this work
ls /mypathname/*.txt
return
thisfile.txt
thatfile.txt
However, notice the path name missing? So when you do a mget
/mypathname/*.* you may get
mget /mypathname/*.*
would you like to get thisfile.txt? y
no such file

The native ftp server for IBM i supports mget /directory/*.*.
Linoma's GoAnywhere does not. They have filed an enhancement
request and they've been pretty responsive in the past. However
they do state that the RFC

is

a little vague on whether or not the list should return the path name.
There is some concern about backward compatibility...
They did some checking around and they are seeing a mix of ftp sites

that

go either way.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.