Closed mvines closed 5 years ago
I've added a https->http redirect via https://github.com/solana-labs/solana-json-rpc-https-proxy/commit/9daa32fd8cf6c174ade3647159b94c5b9b58eef0 for the Blockexplorer API server, and deployed it to the existing "api" https->http redirect instances:
This will allow us to run the Blockexplorer front-end on a service like Heroku that manages SSL certs for us, while preventing modern browsers from blocking https->http accesses into the blockexplorer API server. Conveniently detaching the Blockexplorer front-end will also have the nice side-effect of keeping the Blockexplorer "running" during a cluster restart, which has been an ongoing sore spot.
Next up: connect a Blockexplorer front-end.
Initial cluster-agnostic Blockexplorer front-end has been setup here: https://github.com/solana-labs/blockexplorer-front-end-app
http://explorer.solana.com is now setup, as is http://explore.solana.com The https versions are also available but fail to load due to http/https mixed content issues
We're using http right now, adding support for TLS would be nice. There's two aspects to this issue:
net/
plumbing to preserve certs across deployments