You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by jean-frederic clere <jf...@gmail.com> on 2017/07/10 06:56:41 UTC
rfc1123 aka Proxy balancer://127
Hi,
According rfc1123 the configuration:
ProxyPass "/" "balancer://127"
<Proxy balancer://127>
BalancerMember ajp://tomcat1:8009
BalancerMember ajp://tomcat2:8009
</Proxy>
127 looks valid but it is rejected by httpd, apr_parse_addr_port() takes
127 as port instead hostname.
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?
Cheers
Jean-Frederic
AW: rfc1123 aka Proxy balancer://127
Posted by Plüm,
Rüdiger,
Vodafone Group <ru...@vodafone.com>.
> -----Ursprüngliche Nachricht-----
> Von: Jim Jagielski [mailto:jim@jaguNET.com]
> Gesendet: Montag, 10. Juli 2017 15:33
> An: dev@httpd.apache.org
> Betreff: Re: rfc1123 aka Proxy balancer://127
>
> Personally, I think we simply document that balancer names
> must start w/ a character.
+1
Regards
Rüdiger
>
> > On Jul 10, 2017, at 2:56 AM, jean-frederic clere <jf...@gmail.com>
> wrote:
> >
> > Hi,
> >
> > According rfc1123 the configuration:
> > ProxyPass "/" "balancer://127"
> > <Proxy balancer://127>
> > BalancerMember ajp://tomcat1:8009
> > BalancerMember ajp://tomcat2:8009
> > </Proxy>
> >
> > 127 looks valid but it is rejected by httpd, apr_parse_addr_port()
> takes
> > 127 as port instead hostname.
> >
> > 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?
> >
> > Cheers
> >
> > Jean-Frederic
Re: rfc1123 aka Proxy balancer://127
Posted by Jim Jagielski <ji...@jaguNET.com>.
Personally, I think we simply document that balancer names
must start w/ a character.
> On Jul 10, 2017, at 2:56 AM, jean-frederic clere <jf...@gmail.com> wrote:
>
> Hi,
>
> According rfc1123 the configuration:
> ProxyPass "/" "balancer://127"
> <Proxy balancer://127>
> BalancerMember ajp://tomcat1:8009
> BalancerMember ajp://tomcat2:8009
> </Proxy>
>
> 127 looks valid but it is rejected by httpd, apr_parse_addr_port() takes
> 127 as port instead hostname.
>
> 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?
>
> Cheers
>
> Jean-Frederic
Re: rfc1123 aka Proxy balancer://127
Posted by jean-frederic clere <jf...@gmail.com>.
On 07/10/2017 11:36 AM, Yann Ylavic wrote:
> Hi Jean-Frederic,
>
> On Mon, Jul 10, 2017 at 8:56 AM, jean-frederic clere <jf...@gmail.com> wrote:
>>
>> According rfc1123 the configuration:
>> ProxyPass "/" "balancer://127"
>> <Proxy balancer://127>
>> BalancerMember ajp://tomcat1:8009
>> BalancerMember ajp://tomcat2:8009
>> </Proxy>
>>
>> 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...
Correct the problem isn't limited to the balancer scheme for example:
ProxyPass "/" "ajp://127"
gives:
AH00867: error parsing URL //127: Invalid host/port
So we should we say we are limited to RFC-952 or/and we need the
hostname/balancer names to start with a letter?
Cheers
Jean-Frederic
>
>
> Regards,
> Yann.
>
Re: rfc1123 aka Proxy balancer://127
Posted by Yann Ylavic <yl...@gmail.com>.
Hi Jean-Frederic,
On Mon, Jul 10, 2017 at 8:56 AM, jean-frederic clere <jf...@gmail.com> wrote:
>
> According rfc1123 the configuration:
> ProxyPass "/" "balancer://127"
> <Proxy balancer://127>
> BalancerMember ajp://tomcat1:8009
> BalancerMember ajp://tomcat2:8009
> </Proxy>
>
> 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...
Regards,
Yann.