Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
None
Description
Hello there.
A customer found a possible bug when using IPV6 address.
Problem
When using IPV6 (0:0:0:0:0:0:0:1) in the remote address of all my application defined in Crowd it fails with the following ERROR:
2012-08-02 00:02:09,550 http-8095-5 WARN [crowd.manager.proxy.TrustedProxyManagerImpl] Received invalid IP address: 0:0:0:0:0:0:0:1%0
But the 0:0:0:0:0:0:0:1 is the IPV6 equivalent of 127.0.0.1. After disabling IPV6 from the Network Interfaces all started to work properly.
The %0 was added automatically:
According to RFC 4007, a zone identifier is attached to the textual
representation of an IPv6 address by concatenating "%" followed by
<zone_id>, where <zone_id> is a string identifying the zone of the
address. However, RFC 4007 gives no precise definition of the
character set allowed in <zone_id>. There are no rules or de facto
standards for this. For example, the first Ethernet interface in a
host might be called %0, %1, %en1, %eth0, or whatever the implementer
happened to choose.
Thanks in advance.
Cheers,
Douglas Fabretti
Atlassian Support
