When accessing Kagi from a dual-stack IPv4/IPv6 network and using the IP Address Widget, Kagi fails to perform a IPv4 lookup resulting in the error "IPv4: Failed to resolve." shown to the user.
It appears that when Kagi makes the IPv4 request (GET https://ipv4.kagi.com/api/ip), Kagi forgets to send the Kagi session token/cookie, resulting in a 302 Found being emitted to /signin. Calling this endpoint with a valid cookie returns the expected IPv4 address.
Proof of a dual-stack network.
(Also, it's awesome that Kagi attempts to make a IPv4 call!)
.
