Set DefaultType application/octet-stream in the Web Server configs and let the client figure it out or ...
Ah, so that's what application/octet-stream is for... I get it now :-). Too bad they didn't name it 'application/punt-to-client' ;-)...
LOL, very true that :)
I found it works best on Unix web servers that have lots and lots of Windows binary data and you don't want to know all the MIME codes - so you set that DefaultType and let the client decide HOW they WANT to handle it.
It works because just about *ALL* MIME data has a definable MAGIC number which the properly configured remote clients *should* be able to handle -- I have found a couple of broken clients that garble it (old IE on Solaris, and some broken NS on various older Linux) but generally it is a _dirty trick_ that works...
Bill
-- _Sx_ http://youve-reached-the.endoftheinternet.org/ _____ perldoc -qa.a | perl -lpe '($_)=m("(.*)")' | grep Martian
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
