Magnus added a comment.
Update: CORS is working for the pageview API.
TASK DETAIL
https://phabricator.wikimedia.org/T65808
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: dpatrick, Magnus
Cc: Ricordisamoa, Milimetric, Aklapper, csteipp, Matanya, Jdl
Milimetric added a subscriber: Milimetric.
Milimetric added a comment.
In https://phabricator.wikimedia.org/T65808#1811005, @Magnus wrote:
> Not sure if to add this here or start a new task, but havinf CORS for Labs
> (or anyone) for the new pageviews API, e.g.
>
> https://wikimedia.org/api/rest
Magnus added a comment.
Not sure if to add this here or start a new task, but havinf CORS for Labs (or
anyone) for the new pageviews API, e.g.
https://wikimedia.org/api/rest_v1/metrics/pageviews/per-article/en.wikipedia/all-access/user/Cambridge/daily/20150901/20150930
would be really helpful.
dpatrick added a comment.
This task may be rendered moot if "Access-Control-Allow-Origin: *" is
implemented, re. https://phabricator.wikimedia.org/T62835. Absent that, I think
it would be safe to allow read-only access from labs by adding the domain(s) to
the whitelist (`$wgCrossSiteAJAXdomains
Jdlrobson added a comment.
I wanted to use labs for a small tool I'm working on and alas I cannot use
JSONP nor do I have a @Magnus tool. I've ended up using heruko instead which is
a shame :/
TASK DETAIL
https://phabricator.wikimedia.org/T65808
EMAIL PREFERENCES
https://phabricator.wikim
Magnus added a comment.
FWIW, things have moved on is this particular battleground. Getting a single
cached item using CORS is likely still faster than via API, but I have designed
most of my tools to "collect" items and them retrieve them in batches of 50
from the API, which is quite fast thes