fix: default to https when recovering .eth

[lidel]

Closes #841 – please see it for full context

This PR ensures that navigating to almonit.eth/ or http://almonit.eth/ uses HTTPS URL https://almonit.eth.link/

[lidel]

Note to self: we will be able to recover to http://almonit.eth.ipns.localhost:8080 after #853 lands.

[nachomazzara]

I'm interested in this too. Any update?

Will work for any https://**.eth.link site?

[lidel]

@nachomazzara this will work for all sites, however subdomains will cause HTTPS certificate error, as noted in #841 (comment)

[nachomazzara]

@nachomazzara this will work for all sites, however subdomains will cause HTTPS certificate error, as noted in #841 (comment)

Where the fix should come from?

[lidel]

• short answer: it is up to the operator of HTTP gateway such as https://eth.link to set up a proper certificate for each subdomain.
  • longer answer: only a single level of wildcards is supported in PKI, so additional orchestration is needed to request wildcard certificates for subdomains while they are requested for the first time. gateway operator needs to taken care of this + negotiate with a Certificate Authority if this behavior is allowed (some CA explicitly forbid "mining certificates on the fly" in their ToS). there is also a political aspect: parts of DWeb community are highly adversarial towards PKI and may prefer to spend time and resources on other things. so this is a multi-layered problem.