Access-Control-Allow-Origin header / resolving N2T URLs in the browser from Javascript

[rybesh]

A longstanding issue with N2T URLs is that they cannot be programmatically resolved in the browser using Javascript, because n2t.net does not set the Access-Control-Allow-Origin header (see CORS). It would be great if this could finally be addressed.

Unfortunately, the issue is more complex than just setting the header on n2t.net because n2t.net tends to be just the first server in a long redirect chain. The following servers also need to set Access-Control-Allow-Origin:

• n2t.net:443
• arks.org
• ezid.cdlib.org

I’m not sure if or how I should file issues for the latter two.

[datadavev]

Both n2t.net and arks.org were setting CORS headers after migration from the legacy services, but it appears there has been a regression with a recent update, most likely in the http proxy service. This should be resolved shortly.

Any issues for EZID should be filed with the EZID project at https://github.com/CDLUC3/ezid

[rybesh]

Thank you!