Hi,
there is an apparently relatively well known issue with Apache with PHP
as a module and content-type negociation, whereby the very setup of PHP
as a module for Apache requires that a new (I would say "fake") mime
type x-httpd-php be created, which clashes with content type
negociation, having Apache consider php source file as being of type
x-httpd-php instead of text/html when performing content type negociation.
An illustration of this is http://www.bmt.dnsalias.org/employment, which
actually serves the file employment.php, but will return a 406 Not
acceptable error to the W3C CSS validator, which specifically excludes
all non text/html contents in its request (as evidenced on - mend URL if
broken -
http://jigsaw.w3.org/css-validator/v...1&profile=css2)
Litterature about the subject suggests that configuration of PHP for
Apache with the AddType directive is actually a misconfiguration, and
that PHP should rather be configured with an AddHandler directive,
which, as far as I understand, suggests that it should be run as a CGI
script.
My question is thus to know whether it is possible to somehow mend that
content type negociation issue, while still running PHP as a module.
Thanks in advance,
--
Bertrand Mollinier Toublet
"Reality exists" - Richard Heathfield, 1 July 2003
