Define .php files as text/html not application/x-httpd-php about mime-db HOT 3 CLOSED

Hi @ryandesign! So this is a tricky one, because there is a difference between the PHP file itself (being application/x-httpd-php) and what the PHP file will actually output after being run (typically text/html). I don't think it makes sense to classify .php as text/html in this module, because this is a classification of the actual files themselves, but what they happen to output. Otherwise, .asp, .pl, and more would need to be changed to text/html in this module according to that logic.

If the question is about GitHub Pages, it's good to hear they are using this module to get their extension -> type mappings, but in reality, these are just default mappings. Ideally GitHub Pages should have a way for you to override the type of a given file extension and you could use that to set .php to map to text/html for your use-case.

from mime-db.

Ideally GitHub Pages should have a way for you to override the type of a given file extension and you could use that to set .php to map to text/html for your use-case.

I agree with you. I'll pass your recommendation on to them.

from mime-db.

Haha, I went to see if this was possible, and it lead me to https://help.github.com/articles/mime-types-on-github-pages/ :) Seems like it may not be possible just yet, but may be valuable. We're happy to get anything added, for sure! This is just a weird one is all :) I understand what you are trying to do, which is to keep your linking working, which used to be .php, and I think that makes sense.

from mime-db.