Safari steadfastly refuses to view file???

[Gambuchi]

I don't know, maybe the stars aren't aligned or whatever. I have a website and on it I post files for viewing by members of my church. Actually they are sermons. Prior to reverting )) back to a Macintosh, I maintained this site via a PC. I could go to the site and choose a file to view and IE would allow me to view the file. Safari seems unwilling to allow me to view any file until it has been downloaded. I would like to know how to make Safari just "view" the file rather than downloading it. Is it possible that this is beyond the capabilities of Safari ?? It is my browser of choice.
send reply either by posting here or personal email.
Thanks gang... your'e the greatest group that I've ever belonged to. ::love::

 

[Arden]

What type of file are you using? Some files Safari can open, whereas some files it needs a third-party app while IE might not (PDF's come to mind).

 

[andychrist]

Yeah, if you want to view Word Documents or PDFs in Safari without downloading them:

http://www.schubert-it.com/

And welcome back to Mac!

 

[Gambuchi]

they are all either TextEdit or AppleWorks files. They have a .dat extension which was originally used because the site was maintained by a PC and I posted the files in a format that MicroSoft's WordPad could use. I don't know if there is a workaround or not but if it requires changing all the extensions to something like .cwk or .txt, I am not sure how the multitude of PC users will be able to view the files (if that is even possible)

 

[andychrist]

Look under AppleWorks Help for Creating a Web page. AW can open TextEdit files, so maybe you can convert/export all your files in HTML.
(There has been a recent AppleWorks update:
http://www.macupdate.com/info.php/id/6355 )

 

[Arden]

Most if not all browsers have no problem reading .txt files in one way or another (IE 5 for Mac opens them in the browser window while IE for Windows uses Notepad, I believe), so that would be your best solution.

 

[fbp_]

.txt will open within in browser.

you might want to try .rtf, its just about as compatible plus you get formatting options

 

[Captain Code]

The server probably isn't sending the correct MIME type for the file. The browser doesn't know what file it is, especially if it ends in .dat which can be just about anything.

Setup the server to send the correct MIME type such as text/text for the text files with the name ending in .dat and that will probably allow the browser to figure out what it is.