Using HTTPS gives a weird result. Steps to reproduce: 1. Visit http://gstreamer.freedesktop.org/ 2. Edit the url, to reflect https://gstreamer.freedesktop.org/ Result: After accepting the snake-oil certificate, you end up in an Apache directory listing. Expected result: All the glory of step 1, but then encrypted on transport by a random cerificate. Bug reported earlier and reposted here from https://bugzilla.gnome.org/show_bug.cgi?id=705643
Given there's a snakeoil cert and such, I don't know why you expect this to work. We might do something to SSL-enable all vhosts at some point in the future, but for now I'm closing this as wontfix.
Maybe one could add an https:// -> http:// redirect ?
Given you have to manually go and change http to https in the first place, I think that's a bit pointless.
I ran into the same behavior for other subdomains like http://wayland.freedesktop.org/ . Since there is no https://wayland.freedesktop.org/ or https://gstreamer.freedesktop.org/ I think it would be better to give an HTTP status (error) code like 404.
*** Bug 85625 has been marked as a duplicate of this bug. ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.