QUOTE(Darin McGrew @ Dec 5 2006, 01:10 AM)

IIRC, using AddType like this can send browsers an error
Indeed,
http://httpd.apache.org/docs/1.3/mod/mod_mime.html#addtype says
"The AddType directive maps the given filename extensions onto the specified content type" and
"This mapping is added to any already in force, overriding any mappings that already exist for the same extension". Does this mean that (in Jamie's example) a file with an .html extension will be sent with the content-type "application/x-httpd-php", overriding any existing "text/html" content-type? But when I tested this on some AddType sites with
http://rexswain.com/httpview.html I still seem to get a "text/html" content-type and nothing else.
BTW, isn't AddType a peculiar way of making the server run PHP in e.g. .html files? Why (or how) does it work at all?
QUOTE
unless they include "*" (or "application/x-httpd-php") in their list of accepted types.
My browsers seem to accept "*/*". Which one(s) don't, if one wants to test?
QUOTE
AddHandler leaves the type as "text/html" which all browsers should accept.
I tried that in a .htaccess and it seems to work too:
CODE
AddHandler application/x-httpd-php .html
Is there anything else one should be aware of if using Addhandler for running PHP in .html files?