X-no-Archive:yes
I do not believe that the browser will work the way Reflection FTP does. We
think that IE5 and HP ARPA FTP are a great combination for downloading
files; it sure beats talking someone thru using ftp over the phone! We just
email an ftp protocol link to the user, and they can click it to download.

If you can see the quasi-directory listing (if there is a way to click a
file from this listing to download it, I don't know what it is), then you
must have the
ftp://<UserName>:<Passwd>@<ServerName>:<PortNumber>/FilePath>;TYPE=<TypeCode
>
syntax working just fine for that "FilePath" to the group / directory. Add a
filename (in the correct case to avoid unexpected behaviors), and you should
be able to click the link and start downloading. Note that defaults can be
omitted from this syntax; if you are for instance using the default
PortNumber, you do not need to specify it. We do not use TypeCode, since we
only download bytestream files.

The quasi-directory listings are interesting. We realize that a creative
user could leverage an ftp protocol link to see what other files are
available in our area, so we use a single group and a user that can only
access that group, and only keep files there that any one in that user
community would be free to access. The other issue is the LISTFILE style
listing that ftp returns; this issue has been previously addressed, but any
enhancements to support ls style directory listings would affect this
behavior.