Group: ipernity API development
Changes due to HTTPS migration
![]() |
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 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.
You must be a member of this group to reply to this topic. (Join?)
Jump to top
RSS feed- Latest comments - Subscribe to the comment feed for this topic
- ipernity © 2007-2025
- Help & Contact
|
Club news
|
About ipernity
|
History |
ipernity Club & Prices |
Guide of good conduct
Donate | Group guidelines | Privacy policy | Terms of use | Statutes | In memoria -
Facebook
Twitter