Work has recently been completed in install a Secure Socket Layer (SSL) certificate on the server that powers the IATI Registry.
This will mean that content is now served under the encrypted HTTPS connection. This is in line with internet best practices.
Requests to all Registry URLs using the unencrypted HTTP protocol should be automatically redirected to use HTTPS. This means that there should be no change to user interface functionality. Similarly, API functionality will not be affected, as long as application requests have been set-up to follow redirects, as is common with many request libraries.
Please do let us know below if you have any comments or questions.
provide links to those sources. probably some image/external reference not behind HTTPS
Thanks for the heads up on this Ben - I have flagged this up to Open Knowledge Foundation (the suppliers of the Registry) and have also sent them an article suggesting a fix.
Will post to this forum when this is resolved. In the meantime, please feel free to post if you come across any other issues.