If we're deploying wqds to a wikidata.org subdomain,
- cookies for the domain need to be set for explicit subdomains that need them
- CORS policy needs to be updated to whitelist only subdomains that need it
If we're deploying wqds to a wikidata.org subdomain,
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Isolate wikidata.org cookies and CORS policies | operations/mediawiki-config | master | +3 -2 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T67626 [Epic] Support for queries on-wiki (automated list generation) | |||
| Resolved | Smalyshev | T85159 [EPIC] Deploy a Wikidata Query Service into production | |||
| Resolved | Joe | T107602 Set up a public interface to the wikidata query service | |||
| Resolved | • Deskana | T105196 Security review for Wikidata Query Service code before deploying to production hardware | |||
| Resolved | • csteipp | T90115 BlazeGraph Security Review | |||
| Resolved | None | T108101 Isolate wikidata.org cookies and CORS policies | |||
| Resolved | Bene | T112087 [Bug] m.wikidata.org is not CORS whitelisted | |||
| Resolved | • csteipp | T100413 "You are centrally logged in." toast on every page view on commons | |||
| Open | None | T109538 Vagrant wikis should have mobile site setup when MobileFrontend role is enabled | |||
| Resolved | • Gilles | T54302 Varnish vagrant role |
Change 230247 had a related patch set uploaded (by Legoktm):
Isolate wikidata.org cookies and CORS policies
m.wikidata.org will get fixed with a general mobile fix-- it should already
work for non-js browsers. I just haven't had the time to put in the js fix,
but if wikidata is getting significant mobile traffic, I can up the
priority of that.
It does not right now but that will hopefully change in the next month depending on Bene's work during his internship. He'll make the mobile version work better so we can hopefully then switch to redirecting people on mobile there by default.