Last modified: 2011-10-25 13:19:50 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 T33432, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 31432 - Add a cookie-based preference which redirects all http requests to https
Add a cookie-based preference which redirects all http requests to https
Status: RESOLVED DUPLICATE of bug 29898
Product: Wikimedia
Classification: Unclassified
SSL related (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-06 15:40 UTC by Liangent
Modified: 2011-10-25 13:19 UTC (History)
2 users (show)

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


Attachments

Description Liangent 2011-10-06 15:40:01 UTC
Currently if a user is logging in on https page, when he's coming to Wikipedia by following a link on a 3rd website which points to http version, the page will be in unlogged in state. If he failed to realize this and edited page, his Wikipedia page browsing history and IP address may be leaked. If he realized this, he have to change http to https again and again (unless he's using a 3rd party browser extension).

There can be a resolution: when a user is logging in on https page, set a insecure cookie which says "redirect me to https page", and clear it when he's logging out. In this way, the only disadvantage I can see is one more request and the info for a possible attacker: there's a logged in user at this IP reading this page by following some link on this website.
Comment 1 MZMcBride 2011-10-07 17:02:54 UTC
This is related to, if not a duplicate of, bug 29898.
Comment 2 Roan Kattouw 2011-10-25 13:19:50 UTC
(In reply to comment #1)
> This is related to, if not a duplicate of, bug 29898.
Duping and copying relevant information over.

*** 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