https://bz.apache.org/bugzilla/show_bug.cgi?id=69753
--- Comment #7 from Ruediger Pluem <rpl...@apache.org> --- (In reply to Joe Orton from comment #6) > If the server hostname is an IP literal, does that end up going through the > DNS resolver in the proxy code already? If so, yes, that would break. Hm, we seem to use apr_sockaddr_info_get for doing the DNS resolution, which on Linux seems to use getaddrinfo where the man page states: getaddrinfo() supports the address%scope-id notation for specifying the IPv6 scope-ID. I haven't checked if this would really work on Linux let alone for other OS especially Windows. > > On the wire the hostname used will (almost?) always be the authority string > parsed without the scope, e.g. in a outgoing Host: header. For an outgoing Agreed. > CONNECT to a forward proxy I guess the authority string used *should* > include the scope ID if one has been configured, but that is pretty hairy > territory. Agreed and I think these are edge cases as scope id's are only valid for link local addresses to my understanding. > > The proper way to handle this is likely to parse/store/generate the > authority string separately to the parsed (struct sockaddr) for an IP > literal (which includes the parsed scope), or a DNS-name. This looks like a way forward that we store the scope id separately and add it back in places where needed. I just don't see immediately how we could extend the existing data structures to do this and fit this into the existing flow. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
