Oops, I don't know how I pressed the Send button, sorry!

When I run something like this from the console, I get a CORB error:

$.ajax({url: 'https://whois.toolforge.org/whois/8.4.4.8/lookup/json'}).done(function(data){console.log(data)})

Yet I know there are some tools on labs that are being referenced through JS.

On Thu, Apr 16, 2020 at 4:55 PM Huji Lee <huji.huji@gmail.com> wrote:
Quick question: what does it take for a JS script to be allowed to interact with a toolforge tool?

When I run something like this, I get a Cross-Origin Request Blocked error in the console:


On Tue, Apr 14, 2020 at 6:40 AM billinghurst <billinghurstwiki@gmail.com> wrote:
Checking our interwiki map, we have the following:

wmflabs

Please let us know what it is you want done with these, and for when you would like that scheduled. Thanks.

To also note that we should probably look to update
which lovingly still has the interwiki tswiki:  :-)


-- billinghurst


------ Original Message ------
From: "Arturo Borrero Gonzalez" <aborrero@wikimedia.org>
Cc: "Cloud Services administration and infrastructure discussion" <cloud-admin@lists.wikimedia.org>; "Wikimedia Cloud Services general discussion and support" <cloud@lists.wikimedia.org>
Sent: 13/04/2020 9:25:22 PM
Subject: [Cloud] Toolforge: new domain toolforge.org

Hi!
 
We are happy to announce the new domain 'toolforge.org' is now ready to be
adopted by our Toolforge community.
 
There is a lot of information related to this change in a wikitech page we have
for this:
 
 
The most important change you will see happening is a new domain/scheme for
Toolforge-hosted webservices:
 
* from https://tools.wmflabs.org/<toolname>/
* to https://<toolname>.toolforge.org/
 
A live example of this change can be found in our internal openstack-browser
webservice tool:
 
 
This domain change is something we have been working on for months previous to
this announcement. Part of our work has been to ensure we have a smooth
transition from the old domain (and URL scheme) to the new canonical one.
However, we acknowledge the ride might be bumpy for some folks, due to technical
challenges or cases we didn't consider when planning this migration. Please
reach out intermediately if you find any limitation or failure anywhere related
to this change. The wikitech page also contains a section with information for
common problems.
 
You can check now if your webservice needs any specific change by creating a
temporal redirection to the new canonical URL:
 
$ webservice --canonical --backend=kubernetes start [..]
$ webservice --canonical --backend=gridengine start [..]
 
The --canonical switch will create a temporal redirect that you can turn on/off.
Please use this to check how your webservice behaves with the new domain/URL
scheme. If you start the webservice without --canonical, the temporal redirect
will be removed.
 
We aim to introduce permanent redirects for the legacy URLs on 2020-06-15. We
expect to keep serving legacy URLs forever, by means of redirections to the new
URLs. More information on the redirections can also be found in the wikitech page.
 
The toolforge.org domain is finally here! <3
 
--
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
Wikimedia Foundation
 
_______________________________________________
Wikimedia Cloud Services mailing list
_______________________________________________
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud