GNOME Bugzilla – Bug 699072
CSS file causes mixed content
Last modified: 2013-08-20 15:18:53 UTC
http://www.gnome.org/wp-content/themes/gnome-grass/style.css should be linked as either //www.gnome.org or https://www.gnome.org Firefox is about to implement mixed content blocking (firefox 23), and it's currently active in there development versions (nightly). developer.gnome.org triggers mixed content blocking on quite a lot of pages (ex.): Blocked loading mixed active content "http://www.gnome.org/wp-content/themes/gnome-grass/style.css" @ https://developer.gnome.org/gtk-faq/stable/x669.html Blocked loading mixed active content "http://www.gnome.org/wp-content/themes/gnome-grass/style.css" @ https://developer.gnome.org/gtkmm-tutorial/3.0/sec-menus-popup.html.en Blocked loading mixed active content "http://www.gnome.org/wp-content/themes/gnome-grass/style.css" @ https://developer.gnome.org/gtk3/3.3/gtk-migrating-checklist.html This renders the pages quite hard to navigate with without changing the browser default settings.
I have no issues in Firefox 23; was this fixed already?
Created attachment 251745 [details] Screenshot Nope still broken.
Forgot to mention, that is with a mozilla build of 23 and a clean firefox profile, no changed settings or extensions.
Thanks for your report Cork! we definitely have to switch all the developer.gnome.org's css files to use their SSLed version. Fred, can you have a look into this please?
I see no such http:// link in the library-web module, so I guess a rebuild would to the trick. (there's a --rebuild-all to go over all documents).
Frederic, seems that didn't help and the links are still showing broken, check the above pages with http://www.whynopadlock.com. What else are we missing? Are the above pages still being generated?
git grep "http://www.gnome.org/wp-content/themes/gnome-grass/style.css" returns nothing, so I'm guessing those modules aren't being generated anymore?
I don't know where those links are coming from; but if you look at the file timestamps, you'll know if they are being regenerated, or not. You could then manually remove them, considering newer versions of the docs are available (it would at least work for that gtk3/3.3/ link). There is a google sitemap file that can be used as reference for valid locations.
So, here we go: /srv/http/developer.gnome.org/html/gtk-faq/stable has all the timestamps set to 2011. Not being generated anymore. /srv/http/developer.gnome.org/html/gtkmm-tutorial/3.0/sec-menus-popup.html.en, same as above. /srv/http/developer.gnome.org/html/gtk3/3.3, is not being generated since 2012. Frederic, I'll wait your ack to go ahead and drop the faulty links. Or if you have any other solution, that's welcome.
Nope, just go ahead and remove the directories.
Directories removed.