Last modified: 2014-11-09 16:38:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55131, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53131 - make $wgUseInstantCommons protocol always secure / SSL / https
make $wgUseInstantCommons protocol always secure / SSL / https
Status: UNCONFIRMED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.21.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 73199
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-20 22:05 UTC by Tamer Shlash
Modified: 2014-11-09 16:38 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Tamer Shlash 2013-08-20 22:05:24 UTC
$wgUseInstantCommons protocol appears to be relative according to this bugfix: https://bugzilla.wikimedia.org/show_bug.cgi?id=32219

However, in some countries (like Syria) Wikimedia Commons is blocked if you're using http, so if you're on another wiki that doesn't have ssl, you'll not be able to see any image form the commons, which is really odd.

I think that $wgUseInstantCommons should always use https, I tried to use $wgForeignFileRepos code here: https://www.mediawiki.org/wiki/Manual:$wgUseInstantCommons and changed the apibase to use https and everything worked just fine, it'll be better if just the easy $wgUseInstantCommons use https always.

Thanks.
Comment 1 Sam Reed (reedy) 2013-08-20 22:07:46 UTC
Better is subjective. Some people cannot use HTTPS. There's a lovely discussion of this going on for WMF projects. See https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links