Last modified: 2014-08-10 11:29:03 UTC
If/when we have docs, we can get added to <http://enable-cors.org/resources.html> maybe.
I started [[mw:Manual:CORS]] using an example that Roan posted at bug 20814 comment 15. Would be nice if someone who actually knew how this worked could improve it :)
(In reply to Kunal Mehta (Legoktm) from comment #2)
> I started [[mw:Manual:CORS]] using an example that Roan posted at bug 20814
> comment 15. Would be nice if someone who actually knew how this worked could
> improve it :)
I added a snippet example.
https://www.mediawiki.org/wiki/API:Cross-site_requests https://www.mediawiki.org/wiki/Manual:CORS https://www.mediawiki.org/wiki/Snippets/Cross-wiki_editing_with_CORS https://www.mediawiki.org/w/api.php says this:
origin - When accessing the API using a cross-domain AJAX request (CORS), set this to the originating domain. This must be included in any pre-flight request, and therefore must be part of the request URI (not the POST body). This must match one of the origins in the Origin: header exactly, so it has to be set to something like http://en.wikipedia.org or https://meta.wikimedia.org. If this parameter does not match the Origin: header, a 403 response will be returned. If this parameter matches the Origin: header and the origin is whitelisted, an Access-Control-Allow-Origin header will be set.
centralauthtoken - When accessing the API using a cross-domain AJAX request (CORS), use this to authenticate as the current SUL user. Use action=tokens&type=centralauth on this wiki to retrieve the token, before making the CORS request. Each token may only be used once, and expires after 10 seconds. This should be included in any pre-flight request, and therefore should be included in the request URI (not the POST body).
What else is needed?