This post is to let you know that all Targetprocess On-Demand accounts are now using only a HTTPS connection. This change will go unnoticed by most users since any required redirects will be performed automatically, but we wanted to let you know why we are making this change.
Certainly, using an SSL/HTTPS makes the connection more secure. However, this is not the only reason why we decided to implement this change. Some important infrastructure changes are included to the 3.2 release, such as switching to websockets and enabling the SPDY protocol. These changes require that an HTTPS connection works reliably.
For you, this means better connection, faster load times (especially, the first load) and the ability to have more than 6 tabs of Targetprocess 3 open.
For us, switching to a more modern framework means we can deliver cool features easier.
We know that some of you use custom plugins, reporting services, mashups, integrations, etc. These should not be affected by this change, since we still allow HTTP requests for the REST and SOAP APIs. However, we do recommend updating them to use HTTPS as well. If something goes wrong, please contact our support team.
The changes do not affect local installations (aka On-Site). We do not force HTTPS with On-Site, but it might be a good idea to turn it on as well.