Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Normal
I've gone ahead and made the change I referenced in my previous post: a request from an IPv4-mapped IPv6 address will now be treated as if the request came from a "normal" IPv4 connection. This should clear up the reported issue implicitly for any new IP logs, though it won't change older ones. This also eliminates issues that would be caused by an IPv4-mapped IPv6 address not being considered equivalent to the same IPv4 address (such as with IP bans and some other things that do subnet matching).The reduced space comment was really just an aside. This change actually fixes several other legitimate bugs and reduces confusion if you use a network stack that combines both types of connection into one socket (and unifies the behavior within XF to when distinct sockets are used).
I've gone ahead and made the change I referenced in my previous post: a request from an IPv4-mapped IPv6 address will now be treated as if the request came from a "normal" IPv4 connection. This should clear up the reported issue implicitly for any new IP logs, though it won't change older ones. This also eliminates issues that would be caused by an IPv4-mapped IPv6 address not being considered equivalent to the same IPv4 address (such as with IP bans and some other things that do subnet matching).
The reduced space comment was really just an aside. This change actually fixes several other legitimate bugs and reduces confusion if you use a network stack that combines both types of connection into one socket (and unifies the behavior within XF to when distinct sockets are used).
We use essential cookies to make this site work, and optional cookies to enhance your experience.
See further information and configure your preferences