Closed Bug 272597 Opened 20 years ago Closed 9 years ago

Supported FTP Server Addition: MacOS

Categories

(Core Graveyard :: Networking: FTP, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 224892

People

(Reporter: john, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.4 (KHTML, like Gecko) Safari/125.9
Build Identifier: Mozilla/5.0

Firefox performs a "SYST" check of FTP servers it connects to, and displays a "The FTP server ... is 
currently unsupported" message if the server type is not recognized.  Please add servers that report 
their type as beginning with "MacOS" and "MACOS" to the list of supported servers.

I have performed compatibility testing with Rumpus, a popular MacOS FTP server produced by my 
company, Maxum Development (http://www.maxum.com/Rumpus/) by changing the "SYST" response 
of Rumpus to a supported type in FireFox, and have found no problems at all.  No additional work 
needs to be done to support these servers... "MacOS" simply needs to be considered a compatible 
server.

Reproducible: Always
Steps to Reproduce:
1. Access any MacOS-based FTP server.  An example is "ftp://www.maxum.com/".

Actual Results:  
Firefox reports "The FTP server ... is currently unsupported".

Expected Results:  
Accessed the FTP server as it would any other.
-> Core/Networking:FTP

I don't think that MacOS should be already used as Unix compatible server
because we had problems with incompatible MacOS FTP servers (they didn't match
UNIX FTP listing) in the past.

Can you give me an example FTP Server URL for testing ?
I will add the SYST response from your  ftp Server to the supported list... 
Assignee: bugs → matti
Status: UNCONFIRMED → NEW
Component: File Handling → Networking: FTP
Ever confirmed: true
Product: Firefox → Core
Version: unspecified → Trunk
QA Contact: bmo → benc
matti: silly rabbit, he did, in the url field and in the comment

ftp> open www.maxum.com
Connected to maxum.com.
220-Welcome To Rumpus!
220 Service ready for new user
..
230 User logged in
(command line to send) SYST
215 MacOS Peter's Server
ftp> ls
227 Entering Passive Mode (67,38,123,181,11,188)
150 Opening connection
drwxr-xr-x               folder        0 Nov  4 17:13 100MB test
-rw-r--r--        0        1027     1027 Nov  4 17:25 CheckMark.gif
-rw-r--r--        0        1353     1353 Nov  4 17:25 SpamTrick.htm
drwxr-xr-x               folder        0 Nov 17 18:24 Subfolder A
-rw-r--r--        0        7108     7108 Nov 16 14:54 working.gif
226 Transfer complete

so this is another unix listing currently we have:
1254             ( mResponseMsg.Find("MACOS Peter's Server") > -1) ||
Is it possible we just have the wrong case? otherwise you just need to add the
line w/ the right case for this server (or make find take the insensitivecomparator)
Hi Guys,

First, thanks for the lightning quick, thoughtful review of this problem!  I really appreciate it.

2 things:

1. It is a cases-sensitivity issue.  If I change the name to "MACOS Peter's Server", all is well.  I will 
change the server default accordingly for compatibility with FireFox 1.0.

2. Please consider changing the check to a case-insensitive, "begins with" search for "MACOS".  The 
"Peter's Server" thing is an antiquity.  Peter Lewis wrote the first MacOS FTP server years ago, and since 
then, every MacOS FTP server has been forced to report itself as "MacOS Peter's Server" in order to get 
clients to behave correctly.  I can't tell you how many customers of mine have been confused by this, 
and I look forward to the day when Rumpus can correctly report itself as "MACOS Rumpus".

The case-sensitivity issue is secondary... I can easily work around it.  The "Peter's Server" thing is 
an historical goof that I can also work around, but that should be corrected.

Thanks Again!

John
Assignee: matti → nobody
QA Contact: benc → networking.ftp
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.