Re: [SM-USERS] Browser does not know what to do with index.php

[Robert Pruitt]

Ean Kingston wrote: Stefan Schlörholz said: Ean Kingston schrieb am Mittwoch, 14. Juli 2004 17:34: Stefan Schlörholz said: [cut] Now it is, after I enabled the php module for apache You may also need to make sure that files with .php extensions are treated at type text/html (not application/x-httpd-php) in your Apache mime configuration. I did not do that. It is still application/x-httpd-php and it is working nonetheless. What would be the benefit from cahnging it to text/html? I think it will help some older browsers realize that the data being sent should be displayed as opposed to saved. If it works for you, I wouldn't worry about changing things. It's not up to the browser to know what to do with .php extensions -- it's up to the server. When the server receives a request for a php file, if the setting is set to application/x-httpd-php, it will send the file to the PHP parser, which in turn will send an html page to the browser. If the setting is set to text/html, the server will simply send the file without processing, and the viewer will see raw php code. That's not what you want to have happen. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users