Right click, save this link as - in NS. Every other browser I've used has
a similar method. An easy work around.
>either. But you guys do, Server: Netscape-Enterprise/3.0
The web server is NOT in the picture. It is Browser-FTP Server only.
>I would think there is a server mod you could do to make it
>act correctly.
None that I've aware of, and I've asked in the W3C (I'm a member) and
the folks I no I NS and MS. FTP servers don't send header info. The
browser behavior is to attempt to display any file with an unknown
extension. And if we change the extensions all of the existing code out
there breaks. Since you can work around the download issue but not the
other, that's life.
I believe the long term is to uuencode ComOS. Actually I think the PM-3
code might be that way already, since there was no legacy to deal with.
Let me check... yes, it is.
I believe the last few ComOS revs (since 3.5 I think) can understand
a uuencoded upload. But since there are still so many units running
pre-3.5 we can't safely release new code that way. Eventually what I
expect is something like what you need to do when upgrading from 2.x -
stop in the middle, and move on. Maybe when we go to 4.x code you will
have to be on 3.5 or higher to upgrade... There is time yet.
-MZ
-- Lucent Remote Access Division - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.