from the url:
When the Apache HTTP Server manages its child processes, it needs a way
to wake up processes that are listening for new connections. To do this,
it sends a simple HTTP request back to itself.
So, why apache want to wake up child processes periodically? It can do
this based on event mechanism, only when new request is coming in, the
child will be woken up.
thanks.
On 2017/6/5 ζζδΈ 16:49, Holger Kipp wrote:
You might simply want to google it (e.g. "mod_perl internal dummy
connection")
https://knackforge.com/blog/sivaji/mitigating-apache-internal-dummy-connection-issue
Best regards,
Holger
On 5. Jun 2017, at 08:31, Peng Yonghua <p...@vodafonemail.de
<mailto:p...@vodafonemail.de>> wrote:
I saw many items like these in log,
::1 - - [05/Jun/2017:14:29:06 +0800] "OPTIONS * HTTP/1.0" 200 125 "-"
"Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 mod_apreq2-20090110/2.8.0
mod_perl/2.0.8 Perl/v5.18.2 (internal dummy connection)"
::1 - - [05/Jun/2017:14:29:07 +0800] "OPTIONS * HTTP/1.0" 200 125 "-"
"Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 mod_apreq2-20090110/2.8.0
mod_perl/2.0.8 Perl/v5.18.2 (internal dummy connection)"
::1 - - [05/Jun/2017:14:29:08 +0800] "OPTIONS * HTTP/1.0" 200 125 "-"
"Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 mod_apreq2-20090110/2.8.0
mod_perl/2.0.8 Perl/v5.18.2 (internal dummy connection)"
::1 - - [05/Jun/2017:14:29:09 +0800] "OPTIONS * HTTP/1.0" 200 125 "-"
"Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 mod_apreq2-20090110/2.8.0
mod_perl/2.0.8 Perl/v5.18.2 (internal dummy connection)"
what does it mean? why it exists? thanks.