Consider adding support for a HTTPS gateway

[satazor]

• Version: 0.33.1
• Platform: MacOS
• Subsystem:

Type:

Feature

Severity:

Low

Description:

It would be awesome if we could (maybe optionally) expose a HTTPS gateway alongside the HTTP one. Sometimes, I want to share a web application built with peer-base within a workshop/talk, but it won't work. The reason is that security context is broken because the URL is something like http://<my-lan-ip>:8080/ipfs/<cid> and IPFS fails to boot because window.crypto is not defined.

At the moment, we have to use https://github.com/naugtur/https-proxy-cli.

Steps to reproduce the error:

1. Clone https://github.com/ipfs-shipyard/workshop-todo-dapp
2. git checkout with-peer-base
3. npm i
4. npm run build
5. ipfs add -r build
6. open the folder cid in your local gateway with localhost and see that it works
7. open the folder cid in your local gateway with your lan ip and see that it doesn't work due to window.crypto being undefined

[satazor]

Btw, I've create this here so that we can have a discussion but probably this should be added to go-ipfs as well if everyone agrees.

[pgte]

@satazor do you mean exposing websocket-start rendezvous server through wss://?

[satazor]

@pgte I meant the http gateway to also be exposed in https. It would be awesome to add a DApp built with peer-base in my local IPFS node and share it with people within the same network via http://<my-lan-ip>:8080/ipfs/<cid>. This requires it to be HTTPS otherwise it breaks the security context and window.crypto won't be accessible.

The same thing applies to the exposed WS yes! Related: libp2p/js-libp2p-rendezvous#5

[pgte]

@satazor ha, gotcha!

[achingbrain]

js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide.

This is not planned for Helia but a module that implements this could be written that uses Helia behind the scenes.