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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.3.24                      |1.3.27



------- Additional Comments From [EMAIL PROTECTED]  2003-04-17 14:46 -------
I confirm the same issue.
The real problem here is the dns server not responding timely (slow network,
slow dns server, broken dns servers ...)
The point is to avoid reverse lookups for outgoing connections and maybe in
other situations when:
a) it's totally unneed
b) it might be needed but not mandatory to accomplish the task correctly
After a debating a bit on the devel mailing list I've come up with the
previously attached patch.
Quoted text from the mail:

Hi,
as suggested a while back (I've been a bit busy) by members of this list I
changed the patch so that mod_proxy respects HostnameLookups when dealing
reverse lookups.

I'm not happy with it tough, because I had to add an API funtcion to the apache
core. Since i'm quite new to apache internals here's a question:
Is there an alternative path to follow? If not, what about an API function
similar to ap_get_remote_logname() but that instead of returning a string, works
with the same kind of parameters of *ap_proxy_host2addr()?

Notes:
- in proxy_util.c/proxy_match_ipaddr(): the call to ap_proxy_host2addr() has
been forced to reverse lookups indipendently from configuration settings.
Otherwhise when the parameter for NoProxy is an IP address, it wouldn't have the
same matching it had previously. I think tough, it could be made configuration
dependent.
- in proxy_util.c/ap_proxy_is_hostname(): the call to ap_proxy_host2addr() has
been forced to NOT perform any reverse lookups. It simply doesn't make sense
unless I'm missing something.
- in mod_proxy.c/set_proxy_exclude() and set_cache_exclude(): the calls to
ap_proxy_host2addr() depend on configuration. Probably they could be forced to
NO reverse lookups.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to