Discuss mailing list

["gugus77 AT gmail.com" <gugus77 AT gmail.com>]

I was the one who complained earlier about this script, because it didn't work at all with my IPv6.
Now it displays a result on the page which is nice, thank you !

However you may have "over-fixed" it. I don't say you have done something wrong, I just prefer to inform you, in case it can help improve the service.

Let me explain : all the adresses displayed are now IPv6, and this is not needed in my case. I can configure my network with IPv4 DNSs (even though my external IP is v6).

The problem was that, even though the call to the API returned a result, or so I think (multiple IPv4 in JSON and in a callback function), it couldn't be displayed because the server added a comment to the return data (something like "#do not call this with IPv6", which is not valid in JS). The callback function couldn't be executed.

If the location with IPv6 isn't reliable, and assuming that the results returned but not displayed before this change were accurate, only a simpler fix may have been needed (just removing the comment).

In any case, something is displayed on the front page for IPv6 users now, so the biggest problem is fixed.

On 08/04/2015 05:08 AM, Jeff Taylor wrote:

The nearest-server page (https://www.opennicproject.org/nearest-servers/) and the API page (https://api.opennicproject.org/geoip/) now have support for IPv6 addresses.  Note of course that IPv6 location is still limited, and it could be completely out of whack if you are going through a tunnel, but at least we're making progress.

For the API page, a new variable has been added.  You can now include ipv=[4|6|all] in the URL to dictate what type of addresses you want results for.

--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org