Randall Degges
Randall Degges
That looks awesome. I'll check back. Thanks!
Working on this -- this package is quite old, I'm modernizing it now which means it should fix this shortly. Stay tuned!
This is really odd. This means that your connection was somehow getting the X-Forwarded-For header set to an internal IP (very weird).
The way ipify works is by reading the incoming IP address from the load balancer. So, it's possible this was forged in the TCP request.
This is happening due to the way the headers are being sent. If those headers are modified (X-Forwarded-For) ipify won't get you the right results. In the long-term, something we...
The reason this isn't doable right now is the architecture of the deployment. ipify is deployed to Heroku, which uses a custom load balancer that proxies through the value of...
Re: @benyanke HTTPs doesn't solve this. The service already allows HTTPs access (and insecure, because some legacy devices that use this service don't have libssl), but that won't help if...
Just wanted to clarify things for the sake of transparency.
Working on fixing this.
This is in the works now =) Will update here when I have more news.