Ingress IPv6 not served before reenabling proxy

[hschlote]

Actual Behavior

Deployed application with Apache http server and static page with service and Ingress. Ingress exposed as myapp-myns.localhost on http and https.
Access Ingress with curl -v leads to "Empty reply from server"
curl -4 provides expected result.
We use a company proxy for internet access which is configured and enabled in the proxy section.

Steps to Reproduce

Deploy application with service and Ingress. Ingress exposed as myapp-myns.localhost on http and https.
Access Ingress with

• curl -v
• curl -4

Result

• curl: Empty reply from server
• curl -4: expected result

Expected Behavior

Correct html with curl (IPv6)

Additional Information

Turning off the WSL proxy leads to curl receiving the correct result even with IPv6.
After turning WSL proxy on again still the correct result is received.

Rancher Desktop Version

1.17.0

Rancher Desktop K8s Version

1.30.8

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 Enterprise 23H2 22631.4602

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

VPN Cisco AnyConnect

[hschlote]

The behavior is the same with 1.17.1:
Initially no connection with IPv6, IPv4 works fine.
After switching the proxy off the application can be reached with IPv6, too.
After switching the proxy on again the application can still be reached with IPv6.