Apache 2.2.4 with default httpd.conf and client request /cgi-bin/printenv.pl Get wrong environment value. ..... REMOTE_ADDR="0.0.0.0" REMOTE_PORT="0" ..... I did try fresh install of 2.2.3 and use all default setting. I got the correct value for those two fields in 2.2.3.
We have the same problem. 0.0.0.0 for IP adresses, so you can't use allow or deny. The problem did not exist on v2.2.3
I have the same problem with 2.0.59. I tried to track it down, and I *think* it is a problem with either apr or apr-util. When using 2.0.59 with apr/apr-util 0.9.13 the problem exists. Using apr/apr-util 0.9.12 with the same httpd version the problem goes away. So this might be a problem with apr/apr-util.
Windows 2000 Server (SP4), Apache 2.2.4 and PHP 5.2.0 installed as a module and i get the exact same problem. REMOTE_ADDR="0.0.0.0" REMOTE_PORT="0" Will consider downgrading to 2.2.3 :|
*** Bug 41693 has been marked as a duplicate of this bug. ***
It's same for me. (windows 2000 server + XAMPP 1.6.0a)
We are experiencing the same with Apache 2.2.4 and W2K.
This is resolved (pending code changes) by adding the Win32DisableAcceptEx directive to the httpd.conf file (see http://httpd.apache.org/docs/2.2/mod/mpm_winnt.html)
(In reply to comment #7) > This is resolved (pending code changes) by adding the Win32DisableAcceptEx > directive to the httpd.conf file (see > http://httpd.apache.org/docs/2.2/mod/mpm_winnt.html) Thanks to Bill Rowe for having mentioned this.
(In reply to comment #7) > This is resolved (pending code changes) by adding the Win32DisableAcceptEx > directive to the httpd.conf file (see > http://httpd.apache.org/docs/2.2/mod/mpm_winnt.html) While this may solve the environment issue, using Win32DisableAcceptEx introduces a (known) huge memory leak. So this is not an acceptable workaround. I have downgraden to 2.2.3 for the time being.
All client IPs in the log files (access.log, error.log) are "0.0.0.".
This was solved after 2.2.4 for windows 2000