Last modified: 2013-04-22 16:16:08 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 T45466, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43466 - when serving Uzbek Wikipedia, make HTTPS canonical
when serving Uzbek Wikipedia, make HTTPS canonical
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
SSL related (Other open bugs)
wmf-deployment
All All
: High enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-27 20:03 UTC by Sumana Harihareswara
Modified: 2013-04-22 16:16 UTC (History)
9 users (show)

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


Attachments

Description Sumana Harihareswara 2012-12-27 20:03:56 UTC
Per http://lists.wikimedia.org/pipermail/wikimedia-l/2012-December/123135.html - "should the Uzbek Wikipedia be set up in a way that makes access via the HTTPS protocol the canonical one?"

Tim Starling asked http://lists.wikimedia.org/pipermail/wikimedia-l/2012-December/123142.html :

> Is it enough to set the <link rel="canonical">, or is it also necessary to redirect?

> Either way, the Squid cache would have to be purged, then the search engines would have to reread that site.

Answer http://lists.wikimedia.org/pipermail/wikimedia-l/2012-December/123148.html :

> When I asked the nice folks at Google's search team, they answered me the following:

> * The best answer would for them to use rel=canonical tags so that http://example.wikimedia.uz points to http*s*://example.wikimedia.uz. So I'd send them this page: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=139394 and tell them to start doing that. If they're very serious (and it's a small property, so there's not much risk) then they could make every http page 301 to the https version as well.

> I don't know how much effort each of these two measures would be. If you'd ask me, I would suggest to be "very serious", but we are not under a deadline (the situation has been like this for more than a year now), and setting the rel="caonical" would already be really, really helpful.
Comment 1 Sumana Harihareswara 2012-12-27 20:08:51 UTC
Quim, since you are bug wrangler this week, can you add an RT ticket for this to ask Ops to weigh in?

Chris Steipp wrote:

> I can add a, "I think it's a good idea" to the list, but Ops will need to be ok with the shift. I don't think it would be a problem, but it does mean google spidering our https site, and that may concern them. I think ops would also be the ones to implement the actual change.

(I'm also adding as CC a few other people who have previously requested stuff for Uzbek Wikipedia in Bugzilla, just to help keep the Uzbek Wikimedia community aware of this request.)
Comment 2 Quim Gil 2012-12-27 20:21:06 UTC
RT #4207 has been created.
Comment 3 Tim Starling 2012-12-31 01:19:53 UTC
(In reply to comment #2)
> RT #4207 has been created.

I don't think ops has anything to do here, so I closed that RT ticket. I pushed the relevant feature for review:

https://gerrit.wikimedia.org/r/#/c/41562/

It should be deployed and enabled on uzwiki. Then every page on that wiki should be purged from Squid, say with eval.php.
Comment 4 Nemo 2013-01-06 23:03:03 UTC
(In reply to comment #3)
> https://gerrit.wikimedia.org/r/#/c/41562/
> 
> It should be deployed and enabled on uzwiki. Then every page on that wiki
> should be purged from Squid, say with eval.php.

Note that the configuration in itself has already been fixed by Gerrit change #41561, but the core change is not merged.
Comment 5 Tim Starling 2013-01-07 05:06:34 UTC
Our side of this is done now, the rel=canonical links are deployed. Now Google just needs to crawl it.

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


Navigation
Links