1. I'd head to w3schools and take a few more tutorials.
2. Join programming forums like Daniweb, Stack Overlow and see prior discussions.
3. Google it. Programmers use google. Only your newest programmers get upset over that.
As i understand when the server (e.g. Apache) receives a request it looks for file name extension to find associated mime-type. Then it looks for the handler handling this mine-type (i'm stating it based off adding PHP support to Apache). And here are my questions:
Is the above statement correct?
If so when there is no handler for given mime-type does it mean the default behavior - that is just send a file to the client?
If there is even no explicit extension - mime-type association defined (e.g. .html) the default action again is just send a file to the client?
According to some sources to add PHP support to Apache we have to use
addType directive: AddType application/x-httpd-php .php while others say to use addHandler directive: AddHandler application/x-httpd-php .php which in my opinion is the only correct because addType should be used only for static documents. So why the addType version is still correct?
I found somewhere such a lines:
[CODE]AddType text/html .php .phps
AddHandler application/x-httpd-php .php
AddHandler application/x-httpd-php-source .phps[/CODE]
Does it mean that AddType directive will be used if the server can't find the handler for application/x-httpd-php mime-type and the action would be just to send .php source file to the client with text/html mime-type in response?