|
|
Posted by Leonard Blaisdell on 12/04/05 09:49
In article <Pine.WNT.4.64.0512040701150.1576@ZORIN>,
"Alan J. Flavell" <flavell@physics.gla.ac.uk> wrote:
> But for best results, run a local Apache web server, and browse the
> files via localhost (127.0.0.1). That's what our chief Mac-OSX-based
> web author does, and it avoids lots of different shortcomings that he
> could not solve when he was trying to browse the local file system
> directly.
But that doesn't work for OS9 or less or in what I read the context to
be. I'm not sure which version of the OS his daughter is running. And it
doesn't address the local issues of .txt or .html opening up in what. I
thought that was what the issue was. Drag and drop the file you want on
the application you want, and if the app doesn't recognize it, it won't
open.
I run Apache as (127.0.0.1) on my Mac to illustrate to me what my
scripts will look like in my HTML when I upload them to a UNIX based
ISP. I even have PHP and MySQL available. Wow! Then again, I'm running
OSX.
> Apache then controls the file types issue, and the browser correctly
> responds to the MIME types as the HTTP protocol demands - not to some
> incidental file association defined by the OS. The httpd environment
> can be as close as you bother to make it, to the production server
> where the files will ultimately be served out. Highly recommended.
Agreed.
leo
--
<http://web0.greatbasin.net/~leo/>
Navigation:
[Reply to this message]
|