search

seatgeek / api-support

A support channel for the SeatGeek Platform
9 stars 7 forks source link

IPv6 Support for GeoIP #111

Open Orstio opened 3 years ago

Orstio commented 3 years ago

Hello,

When a network sends an IPv6 address, your API times out trying to geolocate.

This needs to be worked in, as most IPs are switching to over to IPv6.

telrashidi commented 3 years ago

Can you produce the same issue in other internet browsers?

telrashidi commented 3 years ago

May need to increase the maximumAge in regards to enableHighAccuracy. Indication that the application is willing to accept a cached position whose age is no greater than the specified time in milliseconds. for ex. https://dev.fitbit.com/build/reference/device-api/geolocation/

Orstio commented 3 years ago

Browser makes no difference. I do the API calls from PHP, so it is all server-side.

Here is my IPv6 you can use for testing.

2604:3d09:a579:6500:f0ef:cbce:5ae4:22c5

The timeout is not where you should focus. That's a symptom, and how you know there is a deeper problem. The problem is that your system works fine for IPv4 format, but not for IPv6.

Orstio commented 3 years ago

I don't know what makes you think FitBit's API is relevant in any way.

Orstio commented 3 years ago

Here's two examples:

This one works:

https://api.seatgeek.com/2/events?client_id=NDA4MjQ5NXwxNDUyMzYxNjg4&geoip=50.71.217.75&q=football&range=100mi&per_page=5&aid=11813

And this one does not:

https://api.seatgeek.com/2/events?client_id=NDA4MjQ5NXwxNDUyMzYxNjg4&geoip=2604:3d09:a579:6500:f0ef:cbce:5ae4:22c5&q=football&range=100mi&per_page=5&aid=11813