From: http://www.copy-left.net/index.php?itemid=284 view apache2 log, found a large number of:: 1--[25/dec/2009:13:07:51 +0800] "GET/HTTP/1 .0 "302-"-"" apache/2.2.6 (Unix) php/5.2.9 (internal dummy connection) "View the Apache official description as follows:" When Apache HTTP Ser Ver manages its child processes, it needs a way to wake up processes that are the for new listening. To doing this, the IT sends a simple HTTP request back to itself ... These requests are perfectly normal and don't, in general, need to worry about them. They can simply be ignored. The reason for this is the HTTP subprocess, internal dummy connection is because Apache uses the Prefork method, and if you use a worker, you do not use POPs (pipe of death) to communicate between processes, there is no internal Dummy connections.
way to solve:1. Reduce the chance of its happening (modify/etc/apache2/apach2.conf), find Ifmodule Mpm_worker_module This paragraph: startservers 15
Minspareservers 5
Maxspareservers 20
MaxClients 150
Maxrequestsperchild 0 increases the number of maxspareservers (please adjust according to your server's connection), which can reduce the probability of its happening. However, this method is not desirable, depending on the configuration of the server, if too high server will down. 2. Less happens or happens, so take this Request to a fixed web page: Rewriteengine on
Rewritecond%{http_user_agent} ^.*internal/dummy/connection.*$ [NC]
Rewriterule ^/$/blank.html [L] 3. Do not write this information to log: Setenvif remote_addr ":: 1" DontLog
Customlog/var/log/httpd/access.log Combined Env=!dontlog Screen ":: 1", you can filter characters, do not write log. Reference data:
Http://www.linuxweblog.com/blogs/sandip/20080510/apache-internal-dummy-connection
Http://thelinuxguru.blogspot.com/2008/03/apache-internal-dummy-connection.html
This article originates from 51CTO. COM Technology Blog