Group: ipernity API development


Changes due to HTTPS migration


Team
By A Team club
31 May 2024 - 1 comment - 60 visits- Permalink   |   Translate title into English

Dear developers,

the migration of the website to HTTPS also has some consequences for API usage. The API is now reachable via https ://​​api.ipernity.com, and links returned by API requests will be HTTPS. Please update the links to the Ipernity API. Authorization links should be given as HTTPS too (https ://www.ipernity.com/apps/authorize?...). The documentation already shows the HTTPS links.

As some API methods require the POST request method which does not allow redirects, and as some API implementations do not follow redirects at all, the HTTPS redirection for http ://api.ipernity.com has been switched off to enable legacy applications to still function, so the API is now reachable by both HTTP and HTTPS. Note that authorization links will still be redirected to HTTPS, but this is unlikely to cause problems as these links generally are processed by the user's browsers.

In the long run, we want API calls to be encrypted, so we will eventually disable the HTTP access to the API. When this will be done is yet to be decided, the date will be announced in the groups API users and API development.

Your ipernity team

The topic of this discussion has been edited by Team 11 months ago.

Comments
 RCW.
RCW. club
Beware of the space when copying the links - and anyway, the easiest way to change the links is probably adding an "s" before the ":". ;-)
11 months ago.

You must be a member of this group to reply to this topic. (Join?)