If it's an acceptable use-case, I would like to request interoperability between js-ipfs (browser) nodes and the Infura node.
At the moment, the only way js-ipfs browser nodes can connect to go-ipfs nodes is via WebSocket. go-ipfs does support the WebSocket transport as is, if enabled in the config. The current Infura go-ipfs node only configures the TCP transport over IPv6, (which I assume is made to work with IPv4 with an endpoint proxy already in use.)
But browsers only allow pages loaded securely to connect to WebSocket Secure, which go-ipfs currently does not (cannot?) support natively. So, on top of enabling the transport, something needs to wrap that endpoint with a valid SSL setup.
The official issue regarding this matter suggests running nginx as an example proxy. Presumably, the endpoint proxy already in use can also serve that purpose.
If it's an acceptable use-case, I would like to request interoperability between
js-ipfs
(browser) nodes and the Infura node.At the moment, the only way
js-ipfs
browser nodes can connect togo-ipfs
nodes is via WebSocket.go-ipfs
does support the WebSocket transport as is, if enabled in the config. The current Infurago-ipfs
node only configures the TCP transport over IPv6, (which I assume is made to work with IPv4 with an endpoint proxy already in use.)But browsers only allow pages loaded securely to connect to WebSocket Secure, which
go-ipfs
currently does not (cannot?) support natively. So, on top of enabling the transport, something needs to wrap that endpoint with a valid SSL setup.The official issue regarding this matter suggests running
nginx
as an example proxy. Presumably, the endpoint proxy already in use can also serve that purpose.