#587 Add HTTPS support for Virtual HOST service

[Curtis Gedak]

Please consider adding HTTPS support for Virtual HOST service with custom domains.

Ideally this enhancement would work similar to the way you implemented HTTPS support for project web sites, whereby the old
http://PROJECT.sourceforge.net redirects to
https://PROJECT.sourceforge.io.

In the case of VHOSTS with custom domains this might work as follows:

http://example.com ---> https://example.com

Currently SourceForge appears to provide only HTTP support for VHOSTS.

[Christoph Weber]

We will get that set up for you, pending resource availabilty (not before Wednesday this week).
You may have seen that we are already doing this for other important projects, such as Open Office (e.g. https://templates.openoffice.org/)

If we need input and/or help from you - say, website config changes - we will be in touch.

Best regards,
Christoph Weber - Director of Technology, SourceForge

[Curtis Gedak]

Thank you Christoph for your prompt response and consideration.

The VHOST in question is http://gparted.org

Please feel free to let me know if I need to make any web site changes or if I need to do anything else to help make this happen.

Best Regards,
Curtis Gedak - Maintainer of GParted

[Wayne Davison]

Please change your domain's DNS from the current IP of "projects.sourceforge.net" (216.34.181.96) to the IP of "secureprojects.sourceforge.net" (216.34.181.153). Once that is live, you should be able to access https://gparted.org (as well as the current http access). Work through any bugs you find (i.e. mixed content warnings) and then, if you'd like for us to start forcing http -> https, we can turn that on in our config.

[Mark]

Hi,

I was looking at doing this for my project (https://opencamera.sourceforge.io , with the domain opencamera.org.uk, which currently only works with http://opencamera.org.uk , not https). But there's the recent email we got to say that we should update to a new IP (216.105.38.10).

So is the IP required for using https also changing, or will it still be safe to use 216.34.181.153?

Thanks!

[Christoph Weber]

This is a closed issue, so updates won't post properly, but here are my
answers anyway:

1. Yes, please point to the new IP as directed, regardless of protocol.
2. Once our infrastructure rebuild is complete and resources available
   on our side (later this month) we can discuss using your custom domain for
   https://opencamera.sourceforge.io. https://opencamera.sourceforge.io
   We do no have hard and fast rules, but we generally require a decent amount
   of traffic, in particular downloads, on a project to make maintaining a
   custom vhost worth our while. We will let you know. In the meantime, please
   submit a separate feature request for yourself.

Thank you,

Christoph Weber - Director of Technology, SourceForge

On Sat, Feb 10, 2018 at 6:18 AM, mark mdwh2@users.sourceforge.net wrote:

Hi,

I was looking at doing this for my project (https://opencamera.
sourceforge.io , with the domain opencamera.org.uk, which currently only
works with http://opencamera.org.uk , not https). But there's the recent
email we got to say that we should update to a new IP (216.105.38.10).

So is the IP required for using https also changing, or will it still be
safe to use 216.34.181.153?

Thanks!

---

** [feature-requests:#587] Add HTTPS support for Virtual HOST service**

Status: implemented
Labels: HTTPS VHOST
Created: Mon Aug 28, 2017 03:45 PM UTC by Curtis Gedak
Last Updated: Wed Aug 30, 2017 08:55 PM UTC
Owner: Wayne Davison

Please consider adding HTTPS support for Virtual HOST service with custom
domains.

Ideally this enhancement would work similar to the way you implemented
HTTPS support for project web sites, whereby the old
http://PROJECT.sourceforge.net redirects to
https://PROJECT.sourceforge.io.

In the case of VHOSTS with custom domains this might work as follows:

http://example.com ---> https://example.com

Currently SourceForge appears to provide only HTTP support for VHOSTS.

---

Sent from sourceforge.net because you indicated interest in <
https://sourceforge.net/p/forge/feature-requests/587/>

To unsubscribe from further messages, please visit <
https://sourceforge.net/auth/subscriptions/>

[Curtis Gedak]

Thank you Wayne for making it possible to access gparted.org via https://gparted.org.

I made the DNS change you suggested and confirmed that https://gparted.org works. :-)

I have also tested the web site to resolve mixed content warnings.

Please start forcing http -> https for gparted.org.

Thanks,
Curtis

[Wayne Davison]

OK -- http now redirects to https.

[Curtis Gedak]

I tested the http -> https redirect and it works like a charm. :-)

Thank you Wayne, Christoph, and all the folks at SourceForge that make it easier for Free Software projects like GParted to focus on the application while SF handles other key details like web and file distribution services. We appreciate all your hard work.

You guys rock!