Introducing HTTPS for Project Websites

We are very excited to offer HTTPS web hosting to all projects. With a single click, projects can opt-in to switch their web hosting from to Project admins can find this option in the Admin page, under “HTTPS”, naturally 🙂

SourceForge Project Web HTTPS

When a project switches over to HTTPS, the old domain will redirect, so no traffic will be lost or links broken. However, some configuration updates may be necessary if your site contains HTTP references (scripts, image tags, etc). See here for a guide to managing those changes.

This is just one step of many in our continued effort to improve security throughout SourceForge. See our Site News section for a comprehensive list of SourceForge improvements including recent past announcements about multifactor authentication, virus scanning, and more.

Tags: , , , , ,

3 Responses to “Introducing HTTPS for Project Websites”

  1. Markus Nov 30, 2016 at 1:01 pm #

    Why was it necessary to use a different top-level domain for the https project websites?

    • Dave Brondsema Nov 30, 2016 at 3:32 pm #

      The different domain is to make sure project website cookies are kept completely separate from the main site cookies.

      • Thorsten Kani Dec 1, 2016 at 10:52 am #

        good to see goodies like this poppin up from time to time. thanx! PS: Diffin between tags would be nice to see.. Have a nice Day, Thorsten