The purpose of this repo is to better understand the requirements that a webapp must meet in order to connect to a Google Chromecast. Specifically, in regards to protocol (http/https), hostname/ip, network interface (loopback vs physical), point of dns resolution (local, intranet, public).

make image

make run

This will bind to all interfaces on port 80

protocol (http/https), network interface (loopback vs physical), hostname/ip, point of dns resolution (local, intranet, public), and with/without legitimate TLS certificates.

From the above tests, I find there are 3 permitted ways to access a webapp that will not inhibit casting:

• https://[Hostname] - Standard deployment with a legitimate TLS certificate.
• http://[Loopback IP] - Loopback IP can be anywhere within the 127.0.0.0/8 range
• http://localhost/ - Interestingly, if localhost locally resolves to a non-loopback ip it will still work.

This repo on tested the most basic form of casting media. I believe there is another more complicated approach inwhich a second webapp is deployed to be run ON the chromecast itself. And in such a configuration, it will likely have its own constraints for what protocols are permissible.