I switched from ip-api.com to a zero-key API — here's why (HTTPS, CORS, no rate limits)
The article discusses the author's transition from using ip-api.com to a zero-key API for geolocation services. The primary reason for this switch is the limitations of ip-api.com, which only supports HTTP and fails on HTTPS sites. The new API offers several advantages, including HTTPS support, no API key requirement, and CORS compatibility.
- ▪Ip-api.com is a popular geolocation API but only supports HTTP, leading to issues on HTTPS sites.
- ▪The author switched to ippubblico.org, which provides geolocation data without requiring an API key and supports HTTPS.
- ▪Ippubblico.org also offers multilingual responses and has no commercial use restrictions.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3966495) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Vix Posted on Jun 3 I switched from ip-api.com to a zero-key API — here's why (HTTPS, CORS, no rate limits) #webdev #python #api #javascript f you've ever tried to use ip-api.com on an HTTPS site, you've hit this error: "Mixed Content: The page was loaded over 'https', but requested an insecure resource 'http://ip-api.com/json'. This request has been blocked." ip-api.com is the most cited free geolocation API on the internet — Stack Overflow answers, tutorials, GitHub gists.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
