Secure (HTTPS) access to the GBIF API
Hi all,
I'm pleased to announce that the GBIF API is now accessible securely — simply replace http:// with https://.
http://api.gbif.org/v1/occurrence/search → https://api.gbif.org/v1/occurrence/search
This is necessary for anyone embedding the API in a secure website, or where organizational policy requires using HTTPS.
Using the secure API is optional, the non-secure HTTP version will continue to work as before. However, the new GBIF.org website https://demo.gbif.org/ will only be accessible using HTTPS, as this will soon be a requirement¹ for any website accepting passwords.
Please let us know if you encounter any problems with this,
Many thanks,
Matthew Blissett
¹ https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html and https://blog.mozilla.org/tanvi/2016/01/28/no-more-passwords-over-http-please...
participants (1)
-
Matthew Blissett