Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: JWS 3.1.0 SP2 ER1
Affects:Documentation (Ref Guide, User Guide, etc.)
Release Notes Text:The workaround for this issue is to configure the "HttpProtocolOptions" option set to "Unsafe" in httpd.conf
This is a regression as 2.4.23-GA works.
1. Set up httpd mod_cluster balancer with Ipv6 address with advertisement on.
2. Set up worker node (tested with EAP)
3. Checks on console if they correctly connect
Issue was reproduced with EAP-7.1.0.DR17 too. Httpd-2.4.23-GA don't have this issue.
Issue has some connection to ipv6 as some ipv6 tests passed.
2620:52:0:105f:5054:ff:fe22:d46f, 2620:52:0:105f:5054:ff:fe0c:5717, 2620:52:0:105f:5054:ff:feb5:a642, ...
2620:52:0:1040:e8f4:2bff:feef:e504, 2620:52:0:1040:440c:3ff:fee1:df02, ...