Add CORS headers to redirects from individual ORCID resources
After requesting an individual resource (e.g. https://orcid.org/0000-0002-3617-9378) as linked data, the server responds with the following:
$ curl -I -L -H "Accept: text/turtle" https://orcid.org/0000-0002-3617-9378
HTTP 1.1 302 Found
HTTP/1.1 200 OK
While CORS headers are included on the the resource that is redirected to, they are not included in the redirect itself. This makes it impossible to make a cross-origin request for an ORCID resource via the canonical URL.
It would be great if the same Access-Control-Allow-Origin header could be added to the 302 response.
Thank you for your reporting this bug.
Our Dev Team will soon start working to fix this and we will keep you updated here.
ORCID Community Team