3 ms·
A reverse proxy can kind of act as a nice hack around this by multiplexing off of the the Host header (which is unencrypted even with HTTPS due to the way that
by slaymaker1907 9y ago
A reverse proxy can kind of act as a nice hack around this by multiplexing off of the the Host header (which is unencrypted even with HTTPS due to the way that the SSL handshake is done).
- deleted 9y ago[deleted]
- dredmorbius 9y agoThat was my thought. Having the host OS run what's essentially a virtualhost proxy seems like the most elegant, viable-path forward. You'd need a protocol for the guest to announce what site(s) it's planning on hosting, and then bridge those out the the host. Keeping multiple guests from claiming the same name would be useful. Better: shift the whole public layer out to a distributed caching service. Tools such as IPFS offer another possible answer, where the RaPi boxen could be considered simple origin servers.
- lsaferite 9y agoThe HTTPS Host header is not unencrypted. You are talking about SNI which is an extension to TLS that adds the hostname as part of the handshake. The Host header is still encrypted when using SNI.