From cbac7e210c97f60e48b8020985203db58068d74d Mon Sep 17 00:00:00 2001 From: Thomas Sibley Date: Tue, 14 Jun 2022 22:14:28 -0700 Subject: [PATCH] docs: Correct note about CORS In terms of permitting cross-origin requests with the various CORS-related headers, what matters is the configuration of the responding origin. There's nothing the requesting origin (i.e. Auspice here) can do itself. --- docs/customise-client/api.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/customise-client/api.md b/docs/customise-client/api.md index f9d98caf6..81b19d685 100644 --- a/docs/customise-client/api.md +++ b/docs/customise-client/api.md @@ -129,8 +129,7 @@ By default, the client makes API requests ([as detailed here](requests.md)) to " This is using the default server address of "/charon". This can be changed by specifying `serverAddress` in the customisation JSON. -> Note that currently you can't specify a different domain due to CORS headers. -This may well be a simple fix -- please get in touch if you can help here! +> Note that if you specify a `serverAddress` on a different origin (protocol + domain + port) than Auspice, the server will need to send CORS headers to permit the requests from Auspice. ---