Up until now we had only http .. This causes a problem in applications hosted over https because web pages should not mix http and https traffic. In this case requests to the eos node were blocked completely.
I propose that if an httpEndpoint is not provided to Eos.Testnet({..}) and the library is running in a browser, the current url protocol be tested and either the http or https url above be automatically selected. If eosjs is running elsewhere, https should be used.
This change needs to be tested from node and the browser.
The following dawn2 Testnet endpoints are available:
Up until now we had only http .. This causes a problem in applications hosted over https because web pages should not mix http and https traffic. In this case requests to the eos node were blocked completely.
I propose that if an httpEndpoint is not provided to Eos.Testnet({..}) and the library is running in a browser, the current url protocol be tested and either the http or https url above be automatically selected. If eosjs is running elsewhere, https should be used.
This change needs to be tested from node and the browser.