Last modified: 2012-07-20 16:18:02 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 T38456, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36456 - Native "force https" option
Native "force https" option
Status: RESOLVED DUPLICATE of bug 29898
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
unspecified
All All
: Unprioritized enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: ssl
  Show dependency treegraph
 
Reported: 2012-05-02 19:22 UTC by -
Modified: 2012-07-20 16:18 UTC (History)
4 users (show)

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


Attachments

Description - 2012-05-02 19:22:43 UTC
Native option for automatic redirection from http to https.

In other words, merge http://fs.fsinf.at/wiki/SecurePages extension into source code. Plus add relative options to preferences.
Comment 1 Sidney San Martín 2012-05-03 04:28:52 UTC
+1

Also, rIght now it’s possible to log in with HTTPS and then visit (say, from an external link) a Wikimedia page via http and be suddenly not logged in anymore. Change the URL back to https and, presto, you’re logged in again.

It’s great that the authentication cookies are set to secure, but that should really come with a non-secure “hey-please-redirect-me-to-https” cookie.
Comment 2 Krinkle 2012-07-20 16:18:02 UTC

*** This bug has been marked as a duplicate of bug 29898 ***

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


Navigation
Links