On Mon, Jul 10, 2017 at 8:56 AM, jean-frederic clere <jfcl...@gmail.com> wrote:
> According rfc1123 the configuration:
> ProxyPass "/" "balancer://127"
> <Proxy balancer://127>
> BalancerMember ajp://tomcat1:8009
> BalancerMember ajp://tomcat2:8009
> 127 looks valid but it is rejected by httpd, apr_parse_addr_port() takes
> 127 as port instead hostname.
I think apr_parse_addr_port() is more meant to parse some special
httpd directives (which can be port only) than rfc1123's hosts.
> So addr is NULL, then I have:
> "AH01157: error parsing URL //127: Invalid host/port"
> Is 127 really valid, if yes do we plan to fix that?
We probably should use apr_uri_parse() in ap_proxy_canon_netloc(), and
possibly for performance reasons even try to do it one and only once
by request in the whole mod_proxy processing...