blocks|key|3047535|text|mod_php的意思是PHP，作为一个Apache模块。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3047536|基本上，当将mod_php作为Apache模块加载时，它允许Apache解释PHP文件(这些文件由mod_php__解释)。|3047537|在使用Apache时，有(至少)两种运行的方式：|3047538|使用的|3047539|：PHP进程是由Apache启动的，它是解释PHP代码的PHP进程，而不是Apache本身使用PHP作为Apache模块(称为mod_php__)：PHP解释器就像是“嵌入”在Apache进程中:没有外部PHP进程--这意味着Apache和PHP可以更好地通信。|unordered-list-item|3047540|<代码>F218|3047541|然后重新编辑，在评论之后:使用CGI还是mod_php由你决定:这只是你的And服务器的配置问题。|3047542|要知道服务器上当前使用的是哪种方式，可以检查phpinfo()的输出:应该有一些东西表明PHP是通过mod_php+(或mod_php5__)还是通过CGI运行的。|3047543|您可能还想看看函数:它返回web服务器和PHP之间的接口类型。|3047544|如果您检入Apache的配置文件，在使用mod_php时，应该有一个LoadModule行，如下所示：|3047545|LoadModule+php5_module++++++++modules/libphp5.so|code-block|syntax|javascript|3047546|(右边的文件名可以不同--例如，在Windows上，它应该是一个.dll__)|3047547|entityMap|0|LINK|mutability|MUTABLE|url|http://www.php.net/phpinfo^0|0|7|J|8|0|7|0|6|7|1D|7|0|K|4|0|0|3|0|0|3N|1R|7|0|0|8|0|0|A|K|7|0|M|9|1E|7|1O|8|M|9|0|0|0|K|7|Y|A|0|0|W|4|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1L|8|@$9|1M|A|1N|B|D]|$9|1O|A|1P|B|D]]|E|@]|F|$]]|$1|I|3|J|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|E|@]|F|$]]|$1|K|3|L|5|6|7|1T|8|@$9|1U|A|1V|B|C]]|E|@]|F|$]]|$1|M|3|N|5|O|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|6|7|21|8|@$9|22|A|23|B|C]]|E|@]|F|$]]|$1|R|3|S|5|6|7|24|8|@$9|25|A|26|B|C]|$9|27|A|28|B|D]]|E|@]|F|$]]|$1|T|3|U|5|6|7|29|8|@$9|2A|A|2B|B|D]|$9|2C|A|2D|B|D]|$9|2E|A|2F|B|D]]|E|@$9|2G|A|2H|1|2I]]|F|$]]|$1|V|3|W|5|6|7|2J|8|@]|E|@]|F|$]]|$1|X|3|Y|5|6|7|2K|8|@$9|2L|A|2M|B|D]|$9|2N|A|2O|B|D]]|E|@]|F|$]]|$1|Z|3|10|5|11|7|2P|8|@]|E|@]|F|$12|13]]|$1|14|3|15|5|6|7|2Q|8|@$9|2R|A|2S|B|D]]|E|@]|F|$]]|$1|16|3|-4|5|6|7|2T|8|@]|E|@]|F|$]]]|17|$18|$5|19|1A|1B|F|$1C|1D]]]]

<code>mod_php</code> means PHP, as an Apache module.

Basically, when loading <code>mod_php</code> as an Apache module, it allows Apache to interpret PHP files (those are interpreted by <code>mod_php</code>).

 
EDIT : There are (at least) two ways of running PHP, when working with Apache :

<ul>
<li>Using <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" rel="noreferrer">CGI</a> : a PHP process is launched by Apache, and it is that PHP process that interprets PHP code -- not Apache itself</li>
<li>Using PHP as an Apache module (called <code>mod_php</code>) : the PHP interpreter is then kind of "embedded" inside the Apache process : there is no external PHP process -- which means that Apache and PHP can communicate better.</li>
</ul>

 
And re-edit, after the comment : using CGI or <code>mod_php</code> is up to you : it's only a matter of configuration of your webserver.

To know which way is currently used on your server, you can check the output of <a href="http://www.php.net/phpinfo" rel="noreferrer"><code>phpinfo()</code></a> : there should be something indicating whether PHP is running via <code>mod_php</code> (or <code>mod_php5</code>), or via CGI.

You might also want to take a look at the <a href="http://fr2.php.net/manual/en/function.php-sapi-name.php" rel="noreferrer"><code>php_sapi_name()</code></a> function : it returns the type of interface between web server and PHP.

 
If you check in your Apache's configuration files, when using <code>mod_php</code>, there should be a <code>LoadModule</code> line looking like this :

<pre><code>LoadModule php5_module modules/libphp5.so
</code></pre>

(The file name, on the right, can be different -- on Windows, for example, it should be a <code>.dll</code>)

blocks|key|3047577|text|这意味着您必须将PHP作为模块安装在Apache中，而不是将其作为CGI脚本启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3047578|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It means that you have to have PHP installed as a module in Apache, instead of starting it as a CGI script.

blocks|key|312355|text|您的服务器需要安装php模块才能解析php代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|312356|如果你使用的是ubuntu，你可以很容易地用|312357|sudo+apt-get+install+apache2

sudo+apt-get+install+php5

sudo+apt-get+install+libapache2-mod-php5

sudo+/etc/init.d/apache2+restart|code-block|syntax|javascript|312358|否则，您可以使用php：http://dan.drydog.com/apache2php.html编译apache。|offset|length|312359|指定您的服务器操作系统将有助于其他人更具体地回答。|312360|entityMap|0|LINK|mutability|MUTABLE|url|http://dan.drydog.com/apache2php.html^0|0|0|0|C|11|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@$K|10|L|11|1|12]]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Your server needs to have the php modules installed so it can parse php code.

If you are on ubuntu you can do this easily with 

<pre><code>sudo apt-get install apache2

sudo apt-get install php5

sudo apt-get install libapache2-mod-php5

sudo /etc/init.d/apache2 restart
</code></pre>

Otherwise you may compile apache with php: <a href="http://dan.drydog.com/apache2php.html" rel="noreferrer">http://dan.drydog.com/apache2php.html</a>

Specifying your server OS will help others to answer more specifically.

blocks|key|312397|text|此答案取自TuxRadar|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|312398|312399|通过web服务器运行PHP时，有两种截然不同的选择:使用PHP的CGI+SAPI运行它，或将其作为web服务器的模块运行。每个模块都有自己的优点，但总的来说，模块通常是首选的。|blockquote|312400|312401|将PHP作为CGI运行意味着您基本上告诉您的web服务器PHP可执行文件的位置，服务器运行该可执行文件，并为其提供您每次访问页面时调用的脚本。这意味着每次你加载一个页面时，PHP需要读取php.ini并设置它的设置，它需要加载它的所有扩展，然后它需要开始解析脚本-有很多重复的工作。|312402|当你将PHP作为一个模块运行时，PHP实际上位于你的web服务器内部-它只启动一次，只加载它的设置和扩展一次，并且还可以跨会话存储信息。例如，PHP加速器依赖于PHP能够跨请求保存缓存数据，这在CGI版本中是不可能的。|312403|使用PHP作为一个模块的明显优势是速度-如果你从CGI转换成一个模块，你会看到很大的速度提升。许多人，尤其是Windows用户，并没有意识到这一点，他们继续使用php.exe+CGI+SAPI，这是一个遗憾--这个模块通常要快三到五倍。|312404|不过，使用CGI版本有一个关键的优点，那就是每次加载页面时PHP都会读取它的设置。随着PHP作为一个模块运行，您在php.ini文件中所做的任何更改都不会生效，直到您重新启动web服务器，这使得CGI版本更好，如果您正在测试许多新的设置，并希望看到即时响应。|312405|entityMap|0|LINK|mutability|MUTABLE|url|http://www.tuxradar.com/practicalphp/18/6/0^0|5|8|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|13|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

This answer is taken from <a href="http://www.tuxradar.com/practicalphp/18/6/0" rel="noreferrer">TuxRadar</a>:
<blockquote>
When running PHP through your web server, there are two distinct options: running it using PHP's CGI SAPI, or running it as a module for the web server. Each have their own benefits, but, overall, the module is generally preferred.
Running PHP as a CGI means that you basically tell your web server the location of the PHP executable file, and the server runs that executable, giving it the script you called, each time you visit a page. That means each time you load a page, PHP needs to read php.ini and set its settings, it needs to load all its extensions, and then it needs to start work parsing the script - there is a lot of repeated work.
When you run PHP as a module, PHP literally sits inside your web server - it starts only once, loads its settings and extensions only once, and can also store information across sessions. For example, PHP accelerators rely on PHP being able to save cached data across requests, which is impossible using the CGI version.
The obvious advantage of using PHP as a module is speed - you will see a big speed boost if you convert from CGI to a module. Many people, particularly Windows users, do not realise this, and carry on using the php.exe CGI SAPI, which is a shame - the module is usually three to five times faster.
There is one key advantage to using the CGI version, though, and that is that PHP reads its settings every time you load a page. With PHP running as a module, any changes you make in the php.ini file do not kick in until you restart your web server, which makes the CGI version preferable if you are testing a lot of new settings and want to see instant responses.
</blockquote>

blocks|key|3047694|text|要补充这些答案，mod_php是HTTPD服务器中使用PHP的最古老和最慢的方法。除非您运行的是Apache+HTTPD和PHP的旧版本，否则不建议这样做。PHP-FPM和proxy_cgi是首选的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3047695|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just to add on these answers is that, mod_php is the oldest and slowest method available in HTTPD server to use PHP. It is not recommended, unless you are running old versions of Apache HTTPD and PHP. PHP-FPM and proxy_cgi are the preferred methods.

blocks|key|310318|text|mod_php是一个PHP解释器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|310319|从文档中可以看出，mod_php的一个重要特性是，|310320|Mod_php不是线程安全的，它迫使您坚持使用prefork+mpm+(多进程，无线程)，这是最慢的配置|310321|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

mod_php is a PHP interpreter. 

From docs, one important catch of mod_php is, 

"mod_php is not thread safe and forces you to stick with the prefork mpm (multi process, no threads), which is the slowest possible configuration"

While going through a <a href="http://akrabat.com/wp-content/uploads/getting-started-with-the-zend-framework_122.pdf" rel="noreferrer">Zend tutorial</a>, I came across the following statement:

<blockquote>
 Note that the php_flag settings in .htaccess only work if you are using mod_php.
</blockquote>

Can someone explain what that means?

What is mod_php?

服务器

解释器

Windows

在执行时，我遇到了以下语句：请注意，仅当您使用mod_php时，.htaccess中的php_flag设置才有效。有人能解释一下这是什么意思吗？

问什么是mod_php？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是mod_php？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是mod_php？
EN