You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/05/13 17:03:54 UTC
DO NOT REPLY [Bug 9037] New: -
Slow performance when acessing an unresolved IP address through Apache mod_proxy module
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9037>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9037
Slow performance when acessing an unresolved IP address through Apache mod_proxy module
Summary: Slow performance when acessing an unresolved IP address
through Apache mod_proxy module
Product: Apache httpd-1.3
Version: 1.3.24
Platform: PC
URL: http://65.123.25.70
OS/Version: Other
Status: NEW
Severity: Minor
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: fan_xia@hotmail.com
Hi,
Observed a slow performance when using mod_proxy to access an unresolved IP
address. I have setup a web site with the IP address only to test this issue
(http://65.123.25.70) . This is tested by Apache Windows installation. In
order to figure out the problem, I have run a debug in the Apache mod_proxy
source. The following is what I found:
(1)In 'ap_proxy_host2addr' function in the file
of 'proxy_util.c', 'gethostbyaddr' function call is slow because of the
unresolved IP address.
(2)comment out the function 'gethostbyaddr' and set hp=NULL seems fix this
performance issue.
(3)I didn't find any reason why we need to call 'gethostbyaddr' here. Further
analysis is required.
(4)If we do need to call 'gethostbyaddr', I suggest that we make a new
directive to turn on/off this behavior.
regard
Fan
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org