Last modified: 2013-09-04 09:12:35 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 T55703, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53703 - Google points to HTTP articles (where users cannot log in)
Google points to HTTP articles (where users cannot log in)
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
SSL related (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-03 11:47 UTC by tm112
Modified: 2013-09-04 09:12 UTC (History)
1 user (show)

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


Attachments

Description tm112 2013-09-03 11:47:57 UTC
After recent changes in HTTP/HTTPS logging in for users there's a problem*.
Google search results point to HTTP versions of articles but users are not logged in while on HTTP. This enforces users to reload page or re-log in.
I see some solution in bug 51002 ?

*)Although this also occured before but user could login via HTTP (and optionally use a DIY script in common.js to redirect to HTTPS).
Comment 1 Seb35 2013-09-04 07:15:27 UTC
This bug is probably a duplicate of bug 51002, but the resolution of this one has non-trivial implications, see the on-going discussion on wikimedia-l <http://thread.gmane.org/gmane.org.wikimedia.foundation/68103>.

If you are already connected to Wikipedia, you should be redirected from HTTP to HTTPS if you keep checked the preference "Always use a secure connection when logged in" (1st page of preferences). Do you really have this checkbox checked? (if no, disconnect and reconnect after checking.)
Comment 2 tm112 2013-09-04 07:35:42 UTC
Gosh, it works today… I don't know why it didn't two previous times.
Shame on it. Shame on me.
Consider thus bug resolved. Thanks!

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


Navigation
Links