Out of curiosity, do we get the host's address list then using apr_sockaddr_info_get()?

Directives like ProxyBlock and NoProxy need to spin through the alternate address list when they look for a match to the configuration's list.

On Monday, July 30, 2001, at 06:45 PM, Ryan Bloom wrote:

On Monday 30 July 2001 15:30, Graham Leggett wrote:
"Victor J. Orlikowski" wrote:
The dirconn_entry structure is tied to a lot of the functionality of
the proxy.  APR handles in_addr and in6_addr inside of the
apr_sockaddr_t structure, and these are referred to by a void *.

Best we can hope for is to yank any direct mucking with in_addr
structures out, and use APR functions to do it (if the functionality
we desire is available).

As I remember the only part of the proxy where any low level DNS magic was being used was the NoProxy option. Everything else uses APR calls and data hidden inside apr_sockaddr_t.

NoProxy accepts IP address subranges like "192.168." - his needs to be
changed so that it allows IPv6 subranges as well.

Isn't there an APR function that can handle IP address subranges like
this?

Yep. :-) apr_parse_addr_port.


Chuck Murcko Topsail Group http://www.topsail.org/

Reply via email to