[
https://issues.jboss.org/browse/WFLY-6233?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-6233:
-----------------------------------
The fix for this is probably going to be in the log tool, applying to any log statement
which accepts a SocketAddress (or SocketInetAddress) or an InetAddress. See also
https://github.com/wildfly/wildfly-common/blob/master/src/main/java/org/w...
(the {{toURLString}} method, specifically).
/cc [~jamezp]
Format IPv6 addresses with ports in log messages as recommended by
rfc5952
--------------------------------------------------------------------------
Key: WFLY-6233
URL:
https://issues.jboss.org/browse/WFLY-6233
Project: WildFly
Issue Type: Enhancement
Components: Clustering, Web (Undertow)
Affects Versions: 10.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Minor
Doesn't seem to be a violation but per
https://tools.ietf.org/html/rfc5952#section-6
a general recommendation to use [ .. ] format.
{noformat}The [] style as expressed in [RFC3986] SHOULD be employed, and is the default
unless otherwise specified.{noformat}
e.g.
{noformat}INFO [org.jboss.modcluster] (ServerService Thread Pool -- 65)
MODCLUSTER000032: Listening to proxy advertisements on
/ff0e:0:0:0:0:0:0:a:35432{noformat}
{noformat}INFO [io.undertow] (MSC service thread 1-1) UT005039: Undertow starts
mod_cluster proxy advertisements on /ff0e:0:0:0:0:0:0:a:35432 with frequency 10000 ms
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)