Irrelevant

Hello!

Have you tried to use brackets before and after ipv6 adress or {HOST.CONN} macro?

I've just added Template App Apache by HTTP to a host on IPv6. I haven't changed anything else.

In that template, there's an item doing the web check

{$APACHE.STATUS.SCHEME}://{HOST.CONN}:{$APACHE.STATUS.PORT}/{$APACHE.STATUS.PATH}

If I add [] around {HOST.CONN}, it should work with IPs, but it also should break the URL if using a hostname.

Overview

cURL expects any IPv6 hostname in the URL to be in square brackets

http://[::1]:8080/foo

because it needs to know which is the hostname part and which is the port part. We can't guess it automatically. The only thing is to make this configurable.

Below are the options I could think of, I see Option 3 as the cleanest solution.

Option 1

If we would have support for macros in the macro values:

ZBXNEXT-6068

we could add a macro to "App Apache by HTTP" template

{$APACHE.STATUS.HOST} => {HOST.HOST}

which a user could override on the host level

{$APACHE.STATUS.HOST} => [{HOST.HOST}]

and change the URL in Get status item:

{$APACHE.STATUS.SCHEME}://{HOST.CONN}:{$APACHE.STATUS.PORT}/{$APACHE.STATUS.PATH} 

to

{$APACHE.STATUS.SCHEME}://{$APACHE.STATUS.HOST}:{$APACHE.STATUS.PORT}/{$APACHE.STATUS.PATH} 

Pros

• user will be able to override the macro on the host level

Cons

• additional functionality to implement
• no automatic handling

Option 2

Move the whole URL of the Get status item to the macro:

{$APACHE.STATUS.URL} => http://{HOST.CONN}:80/server-status?auto

Pros

• user will be able to override the macro on the host level

Cons

• no automatic handling

Option 3

Add support of new macro function to format the hostname part of the URL, e. g. urlform():

{{HOST.*}.urlform()} => returns "DNS", "IPv4", "[IPv6]"

Pros

• automatic handling

Cons

• additional functionality to implement

Option 4

Add new macro e. g.

{HOST.CONNURL} 

that will return IPv6 address in square brackets.

Pros

• automatic handling

Cons

• additional functionality to implement

Option 5

On level of substitute_simple_macros() detect that it's URL situation and add square brackets automatically.

Pros

• automatic handling

Cons

• additional functionality to implement
• implement for each place where used

Additional thoughts

Implement (probably not in the scope of this task) escaping of macro values.

{ITEM.LASTVALUE1.escape(<rules>)}

Also would be nice to add support for macro functions to all macros.

Decided today that in order to fix this properly new functionality (ZBXNEXT) needs to be introduced first.

The only solutions for now that I see is:

• editing URL field of Get status item on the host that uses IPv6 and adding square brackets around {HOST.CONN}
• creating a copy template for IPv6 hosts with square brackets around {HOST.CONN}