The support.orcid.org website is on a UserVoice platform that has a different privacy policy from our other sites. You may view the details at http://support.orcid.org/tos
X

I suggest that...

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
Location: https://pub.orcid.org/experimental_rdf_v1/0000-0002-3617-9378
...

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
...

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.

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Patrick Golden shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  AdminORCID (EMEA) (Admin, ORCID) responded  · 

    Thank you for your reporting this bug.

    Our Dev Team will soon start working to fix this and we will keep you updated here.

    Kind regards,
    ORCID Community Team

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base