Re: MacOS9.1, URL Access Scripting and FTP Uploads
Re: MacOS9.1, URL Access Scripting and FTP Uploads
- Subject: Re: MacOS9.1, URL Access Scripting and FTP Uploads
- From: Evan Gross <email@hidden>
- Date: Thu, 10 May 2001 22:27:06 -0400
>
Anyone got any experience of using MacOS 9.1, URL Access Scripting 2.2.1 and
>
URL Access Extension 2.3 for uploading file to FTP servers?
Sorry I didn't see this message earlier, but I *think* you've run into a bug
in URL Access (at least I've reported it as such, and confirmed it's a URL
Access bug to my satisfaction - no word from Apple yet) that was introduced
in URL Access 2.2.
Or should I say you've run into one of a few different bugs related to FTP
transfers.
Here's a brief summary of the nasty things I've found in URL Access 2.3 and
URL Access on OS X (it's version 3.0, but seems to behave just like 2.3
does):
1. (This is the one you may be running into - it works with URL Access 2.1
but not with 2.2 or later - I verified this by installing 2.1 on OS 9.1) If
you disable FTP Passive mode in the Internet Control Panel's file transfer
settings, URL Access always fails when it tries to log onto the FTP server
(ANY server). It issues a bogus PORT command with 0,0,0,0 as the first 4
parameters instead of a valid IP address. After that, the server either
returns an error or URL Access just spins forever. Very "not good". In other
words, URL Access 2.2 or later cannot perform non-passive FTP transfers AT
ALL.
2. You can't use a "short form" FTP URL with URL Access. This means that for
users with accounts and their own "home" directory on an FTP Server you
can't specify a relative path in the URL. This is a bug in URL Access where
it (incorrectly) uses the first "/" following the host-name as part of the
initial CWD command it sends after logging on. So if user "joe" has their
own directory on the server, say "/users/joe/" and the URL is
"
ftp://joe:email@hidden/mydocs/"; URL Access does a CWD "/mydocs"
(absolute, from root, which won't exist) instead of CWD "mydocs" and will
then fail to transfer (up or download) to that URL (/users/joe/mydocs/).
3. URL Access totally fails to log onto some FTP servers anonymously (some
weird positive error code (13, I think) is often returned). Some servers
(and it's legal) return their responses in two "packets" - the numeric
response (generally the important thing) and then the (sometimes optional)
textual response followed by the line ending. This trips up URL Access,
which doesn't seem to wait for the CR/LF to signal the end of a server
response. It takes the first "piece" with the numeric code and then
continues on its merry way. Result equals bogus error codes and failed
logins (and therefore failed transfers).
I've reported every single one of these bugs and their status hasn't changed
since I've submitted them. They are all easily reproducible with 9.1's
Network Browser.
Hope this helps, but if none of these describes your problems let me know,
I'll file yet another bug report...
Evan Gross
Rainmaker Research Inc.
--
+------------------------------------------------------------------------+
| Evan Gross, Rainmaker Research Inc. <
mailto:email@hidden> |
| - Developers of Macintosh and Windows Software - |
| Spell Catcher 8 for Mac OS and Windows from Casady & Greene, Inc. |
| Visit <
http://www.spellcatcher.com> |
| Aladdin Transporter from Aladdin Systems, Inc. |
| Visit <
http://www.aladdinsys.com> |
| The DiskTools Collection for Mac OS, shareware |
| Visit <
http://members.home.net/rainmakerinc> |