William A. Rowe, Jr. wrote:
Joe Orton wrote:
The previous behaviour makes far more sense, and it would not be
unreasonable for applications to rely on it. In fact it looks like
the APR_IPV6_ADDR_OK flag is exactly a case which relies on that
behaviour, and is now presumably broken.
Interesting. So, if we modify this to honor only the case of
APR_IPV4_ADDR_OK plus the APR_INET6 family, it would satisfy you?
Patch committed, please examine and see if this covers your concern?
Of course at this point, it's not possible to do so with a trivial
patch, since apr_sockaddr_ip_get never sees that flag.
Ignore me as usual, quoting the wrong side of the equation.
