Glad to hear I'm no the only one having this problem... 

The best I can make of it is that there is something wrong with php that
causes the by-the-book installation to fail.  Since apache is compiling,
and it works fine when the php mime types are commented out of httpd.conf,
it leads me to believe that the error is on php's part-- it seems that
apache is successfully handing the processing of the php mime types over
to php, but php is failing to deal with them properly, so it servers up
garbage of some sort, that the browser can only interpret as an unkown 
mime type, causing the save-as.  This is really just speculation.  

I find it very disapointing that there are no documents anywhere on the php 
site addressing this problem, which appears to be very much a problem with php.
help!

thanks
todd 

On Fri, 19 Jan 2001, Norman Bollinger wrote:

> 
> 
> I'm having the same problem and so are others on this list.
> 
> My problem is how do you debug this thing.
> What is the input process and output.
> 
> Apache/php is delivering something to the browser that he does not 
> understand. that appears to be the mime type.
> Why is he doing that?
> 
> Norman
> 
> 
> On Thu, 18 Jan 2001, Todd Goldenbaum wrote:
> 
> > hi,
> > 
> > does anyone know what it means if, after installing php4 and apache 1.3.9,
> > any php file prompts a 'save as' dialog from the browser?  it's as though
> > my httpd.conf mime-type lines about .php files and so on are spawning
> > >something< to happen, but instead of the right thing, it's a save as 
> > dialog.  any help appreciated.
> > 
> > thanks,
> > todd
> > 
> > 
> > -- 
> > PHP Install Mailing List (http://www.php.net/)
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 


-- 
PHP Install Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to