This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 460
Testnet is not accepting CORS browser requests #6
Comments
fyi: the challenge is in the load balancer |
possibly related: EOSIO/eos#376 |
Work-around: Eos.Testnet({httpEndpoint: 'http://t1readonly.eos.io'}) |
jcalfee
pushed a commit
to EOSIO/eosjs-api
that referenced
this issue
Mar 12, 2018
changed default to: http://t1readonly.eos.io |
is there a https endpoint ? |
I'm asking to see if we can get https setup.. |
Ok, https is enabled now, please try: https://t1readonly.eos.io/ |
Closed
metamaster2021
pushed a commit
to armoniax/eosjs
that referenced
this issue
May 7, 2022
readme, license, contrib
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The latest Eos.Testnet() points to a http://testnet1.eos.io which is not accepting CORS requests yet. So it works in node but not in the browser.
In the mean time: http://t1readonly.eos.io is setup with CORS. I'm told it will however silently fail if a large smart contract (setcode) is attempted.
The text was updated successfully, but these errors were encountered: