Welcome! Log In Create A New Profile

Advanced

how h1_frt_addr is defined during reg tests?

Posted by Илья Шипицин 
Илья Шипицин
how h1_frt_addr is defined during reg tests?
July 11, 2018 09:20PM
Hello,

I'm playing with reg tests. Sometimes they fail for weird reasons.
(for example, fedora 28 on gitlab ci)

https://gitlab.com/chipitsine/haproxy/-/jobs/81106855


curl -i -k https://${h1_frt_addr}:${h1_frt_port}

became

curl -i -k https://::1:38627

which is not correct.
but I could not find any definition of h1_frt_addr, how is it defined?
Frederic Lecaille
Re: how h1_frt_addr is defined during reg tests?
July 12, 2018 10:40AM
On 07/11/2018 09:12 PM, Илья Шипицин wrote:
> Hello,
>
> I'm playing with reg tests. Sometimes they fail for weird reasons.
> (for example, fedora 28 on gitlab ci)
>
> https://gitlab.com/chipitsine/haproxy/-/jobs/81106855
>
>
> curl -i -k https://${h1_frt_addr}:${h1_frt_port}
>
> became
>
> curl -i -k https://::1:38627
>
> which is not correct.
> but I could not find any definition of h1_frt_addr, how is it defined?

Well, it is defined thanks to varnish lib APIs. The correct syntax
should be curl -i -k https://[::1]:38627 in this case
(https://www.ietf.org/rfc/rfc2732.txt).

But h1_frt_addr could also be defined as 127.0.0.1 I guess on hosts
where ipv6 is not enabled.

So could you try this patch attached to this mail? Note that with this
patch the test is a bit faster.

Fred.
Илья Шипицин
Re: how h1_frt_addr is defined during reg tests?
July 12, 2018 10:50AM
yes, it fixed build:

https://gitlab.com/chipitsine/haproxy/-/jobs/81225803

чт, 12 июл. 2018 г. в 13:28, Frederic Lecaille <[email protected]>:

> On 07/11/2018 09:12 PM, Илья Шипицин wrote:
> > Hello,
> >
> > I'm playing with reg tests. Sometimes they fail for weird reasons.
> > (for example, fedora 28 on gitlab ci)
> >
> > https://gitlab.com/chipitsine/haproxy/-/jobs/81106855
> >
> >
> > curl -i -k https://${h1_frt_addr}:${h1_frt_port}
> >
> > became
> >
> > curl -i -k https://::1:38627
> >
> > which is not correct.
> > but I could not find any definition of h1_frt_addr, how is it defined?
>
> Well, it is defined thanks to varnish lib APIs. The correct syntax
> should be curl -i -k https://[::1]:38627 in this case
> (https://www.ietf.org/rfc/rfc2732.txt).
>
> But h1_frt_addr could also be defined as 127.0.0.1 I guess on hosts
> where ipv6 is not enabled.
>
> So could you try this patch attached to this mail? Note that with this
> patch the test is a bit faster.
>
> Fred.
>
>
Sorry, only registered users may post in this forum.

Click here to login