1/19    How do I configure apache so that all the files in certain
        directories are executed as PHP without the ugly .php extension?
        \_ Turn on MultiViews; you can leave the files with the .php
           extension, but just access them without using the extension.  -tom
           \_ Oh goodie, someone talking about MultiViews.  Are there any
              potential problems with turning them on I should be aware of?
              - !op
              \_ I suppose it makes it marginally easier for someone to
                 guess one of your URLs.  There is some potential confusion
                 if you have two files with the same base name in the
                 same directory.  But I don't think there are significant
                 issues.  Our site has been that way for several months:
                 http://ls.berkeley.edu/lscr.  -tom
              \_ MultiViews are not the rigut solution for that. They use content
                 negotiation, IIRC and that causes problems with validation and
                 old browsers. I'd recommend using URL rewriting. in your
                 .htaccess put something like:
                 Options -MultiViews
                 RewriteEngine on
                 RewriteCond   %{DOCUMENT_ROOT}%{REQUEST_URI}.php -f
                 RewriteRule   .* %{REQUEST_URI}.php
                 \_ How does MultiViews cause problems with validation or
                    old browsers?  It's transparent to the client unless
                    the client asks for something specific in content
                    negotiation.  -tom
                    \_ I thought it used to. Apparently I was wrong.
                       By the way http://ls.berkeley.edu/lscr does not
                       pass validation at http://validator.w3.org
                       \_ It validates in HTML Tidy.  I'll look at the
                          issues http://w3.org brings up.  -tom
                          \_ Update for those who care: It looks like HTML
                             Tidy only validates against HTML 1.0 Transitional,
                             even if the DOCTYPE is HTML 1.1 Strict.
                             The 1.1 Strict warnings include stuff for
                             backwards compatibility with not-very-old
                             browsers (IE 5.5), so we may look at falling
                             back to 1.0 Transitional.  -tom
                             \_ Do you mean XHTML rather than HTML?
                                also there is no "XHTML 1.1 Strict."
                                just XHTML 1.1   fwiw.
                                \_ Yes, I mean XTHML.  -tom
        \_ Do your files have an extension now?  If it's, e.g. ".html", you
           could just toss this into your .htaccess:
           AddType application/x-httpd-php .html
           --dbushong