Re: URL Access Error codes
Re: URL Access Error codes
- Subject: Re: URL Access Error codes
- From: Malcolm Fitzgerald <email@hidden>
- Date: Fri, 15 Mar 2002 13:34:42 +1100
on 15/3/02 12:41 PM, John W Baxter at email@hidden wrote:
>
Malcolm Fitzgerald <email@hidden>
>
> on 15/3/02 12:38 AM, JollyRoger at email@hidden wrote:
>
>
>
>> On 3/14/2002 1:18 AM, "Malcolm Fitzgerald" <email@hidden> wrote:
>
>>
>
>>> 1. The server. We used to send things to upload.zipworld.com.au now
>
>>> we send things to our domain name
>
>>>
>
>>> 2. our login is now our full email address, previously it was simply
>
>>> our account name. That means there are two @ symbols in the URL. URL
>
>>> Access chokes on that, so I'm sending it in a converted state.
>
>>
>
>> Error -3170 is an Open Transport (OT) error:
>
>>
>
>> -3170 kOTBadNameErr The endpoint name is invalid.
>
>>
>
>> So this is a connection problem of some sort. My guess is OT is not able to
>
>> figure out what part of the URL is the username and what part is the domain
>
>> name. Was the FTP protocol ever *designed* to allow @ characters in
>
>> usernames??? I kind of doubt it. Maybe you should talk to your FTP admin
>
>> about changing your FTP username to a simple username.
>
>>
>
>
>
> Well the @ character has had my antennae prickling. I have used the
>
> constructed URL in Interarchy - it works. So, Interarchy and URL Access
>
> handle the URL differently and whatever Interarchy does is good enough for
>
> the server. (But we've only got one licence for interarchy and we're going
>
> to use the script across six machines. We're poor but honest folk!)
>
>
>
>> HTH
>
>>
>
>> JR
>
>>
>
>> PS: You know, I've seen this problem here once before recently. It seems
>
>> fairly uncommon to me for an administrator to use an @ character in a
>
>> username. I have to wonder why a sys admin would ever ask users to use an
>
>> email address rather than a standard username. I don't see how using email
>
>> addresses is much more secure than using usernames. The common security
>
>> problems with FTP servers typically have to do with buffer overflows, etc.
>
>> Could it be that the person maintaining this FTP server is a Mac OS/Winblows
>
>> user who doesn't really know much about FTP servers running some dinky FTP
>
>> server on his machine? Just curious - I'm interested in learning what is at
>
>> the bottom of this circumstance.
>
>
Last time this came up, I *think* we concluded that URL access can't do the
>
job.
!!! Aaaaargh !!!
>
Apple really needs to attend to this, because the problem will grow
>
(ISPs are rapidly merging) rather than going away.
>
I've been running Interarchy's network traffic watcher to see whats
happening. Using URL Access Scripting (UAS) there is no traffic at all. UAS
tosses up the error without trying to communicate. It does give two
different error messages depending on whether the initial @ is encoded.
I'd think the solution would be to allow the user to use URL or named
parameters (server, user, password, path, etc) so that it doesn't have to
make any decisions itself.
Now, if I could get some assurance from Apple that they'll have a fixed
version out by Monday I'll put down the headache pills and take some of the
strain off my liver. :-(
--
yours
Malcolm Fitzgerald
Database Manager
The Australian Society of Authors
ph:02 93180877
fax:02 93180530 email@hidden
http://www.asauthors.org
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.