From September 2017 on access to BibSonomy will only be possible via
TLS encrypted connections (that is, HTTPS). BibSonomy’s REST API
support HTTPS for some time and in September 2016 we had introduced
SSL support for the BibSonomy web pages. This ensures that all your
data is encrypted on the way to your browser to protect your
privacy. In September we will disable unencrypted access to BibSonomy,
that is, all non-encrypted (HTTP) requests to BibSonomy will be
redirected using HTTP 301 responses to the corresponding HTTPS (SSL)
pages. For browser-based access this should not make any difference,
however, some plugins and extensions that are using the REST API might
be affected by this.
BibSonomy integrates well with other services and tools but the
underlying source code might not be able to properly resolve the HTTP
redirects, yet. Therefore, in case your service or tool is relying on
a connection to BibSonomy, please check whether it properly supports
HTTP redirects or migrate it directly to use HTTPS (which is our
suggestion). We have already migrated the PHP client library as well
as the Typo3 extension. The Python and Ruby clients also already
support HTTPS. The source code of other extensions is available on BitBucket and we appreciate any help in the migration effort. Please
submit pull requests for the libraries and tools you are using.
We hope that our move towards encrypted-only access does not cause any
problems and that you will have enough time until September to migrate
your code.