GNOME Bugzilla – Bug 761673
website not SSL-enabled
Last modified: 2016-02-18 16:13:04 UTC
I've been enabling SSL across the fd.o websites, and I've not been able to properly enable it for GStreamer as the site contains a huge number of hardcoded non-SSL references: root@annarchy:/srv/gstreamer.freedesktop.org/www/htdocs% grep http://gstreamer.freedesktop.org/ index.html | wc -l 69 For example, this includes the CSS which triggers mixed-content warnings. If these links were converted to either relative or just SSL-only, we could switch the site over.
The way things are set up, it's a bit awkward to convert things to relative URIs. I can easily change everything to https:// though. Can we also make it redirect http:// -> https:// somehow? (via .htaccess or whatnot)
PS: thanks for working on this!
At the moment they're both serving the same site, so if you push a change to make them all https, I'll turn the (currently-disabled) redirect back on and that should be a smooth transition.
Why is it awkward to fix for both though? Couldn't we just use relative URLs everywhere?
Because we use &site;/foo/bar basically everywhere, which will be replaced with the site address. I don't see anyone converting all of those to relative URIs though. I'm also not sure it's desirable in all cases.
Can &site; not just expand to nothing? Having both HTTP and HTTPS sites means that we have to maintain (and test) two separate configs - more work whenever we need to change anything, and one more thing to go wrong.
Also, our preference is for HTTPS-only sites; changing the 'site' expansion to the HTTPS variant will work (as plain-HTTP will load HTTPS resources) without breaking the reverse (HTTPS site will never load plain-HTTP resources). So if you just push that change then we should be safe for the transition.
(In reply to Daniel Stone from comment #6) > Can &site; not just expand to nothing? > > Having both HTTP and HTTPS sites means that we have to maintain (and test) > two separate configs - more work whenever we need to change anything, and > one more thing to go wrong. I don't think there's any problem with just making &site; = "". Everything should just convert to absolute paths without a hostname and work fine, right?
Done. Seems to work fine :) commit 0cbafe8d73f3f8d5ed628c22422086746b87072e Author: Jan Schmidt <jan@centricular.com> Date: Fri Feb 19 03:04:46 2016 +1100 Make the site entity = "" on the live site. That makes all links simply be absolute paths on the server. Keep using the &site; entity for local builds, so a top-level path can be prepended. https://bugzilla.gnome.org/show_bug.cgi?id=761673
Yep, and now enabled for pure HTTPS. Thanks Jan!