This is because, conceptually, foo.php doesn't have any information to distinguish that the results of running foo.php are html.
You might try using the AddOutputFilter instead of the antique methods of associating application/x-httpd-php - because that 'content-type' is meaningless to the outside world. This is why Apache allows you to associate filters by extension without creating ByType associations for content filters. One alternative, if that doesn't work well for you, is to use a wildcard <Files "*.php"> section with a SetOutputFilter directive. So - adding the PHP output filter by .php would solve that problem - your next problem is associating php with html. Two options; One, name your file foo.html.php. Or you can do the SSI thing, with a filetype .phtml (like .shtml). Or you can simply declare that .php is text/html, which I'm guessing 99% of your PHP scripts create. Just some random observations... Bill At 11:49 PM 1/31/2003, Stephen van Egmond wrote: >I've been looking through mod_negotiation.c to resolve a problem >I have with PHP and Google. > >The issue is that Google sends > Accept: text/html,text/plain > >And Apache, configured with PHP as a module, is unable to negotiate a >satisfactory mime type since PHP is registered under >application/x-httpd-php rather than the text/html it typically serves, >then serves a 406 to google. > >Now here's where I start guessing. > >Currently mod_negotiation.c uses a pseudo_html flag to treat two mime >types (text/x-server-parsed-html[3] as if they were text/html. >Theoretically, if I bash PHP's signature into there, it should work, >right? > >(I say theoretically, because I've done it, and it didn't work. Or at > least I'm pretty sure I've done it - the .deb source is tricky.) > >-Steve
