Subdomain support for providing secure context when hosting websites

[agazso]

Summary

It would be good if Bee supported subdomain access (e.g. http://<cid>.localhost:1633) so that websites can be served in a secure context.

Motivation

This is important when using with the swarm-extension so that websites can be served in a secure context, but also to not break the path for assets, as is the case by prepending /bzz/<hash> when accessing assets.

Implementation

The implementation would depend on adding two things two Bee:

• CID support (something similar to what swarm-cid-js is doing)
• Subdomain support so that a HTTP Host header field can be interpreted in the form of http://<cid-or-ens>.localhost:1633 and resolved internally as if it was accessed through the /bzz endpoint.

Drawbacks

It makes Bee more complex and adds more dependencies (e.g. CID support). An alternative could be to use the gateway-proxy for this, however that would add an extra dependency for people who are using the swarm-extension, therefore this complexity would be pushed on the users.

See also previous issue #1502

[agazso]

Related PR: #2970