HomeFAQsCORS request did not succeed

CORS request did not succeed

When writing a browser based Ethereum Javascript application one often experiences issues in conjunction with messages such as:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://website.com/. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://website.com/. (Reason: CORS request did not succeed).

Kaleido users often experience CORS (Cross-Origin Resource Sharing) problems when serving browser Javascript from their site that sends requests to their Kaleido nodes. This problem occurs due to the “same-origin policy” which prevents one domain from requesting resources from another domain, for example requests from mysite.com to u0xjzji-u0sfwew-rpc.kaleido.com.

Kaleido has recently remedied this issue by setting a liberal “Access-Control-Allow-Origin” that allows any domain to make requests to any Kaleido RPC node. Therefore, environments with releases greater than 0.1.11 will not experience CORS problems.