Support "in-room" template when behind CloudFlare

[mithro]

Previously we used X-Forwarded-For but CloudFlare doesn't seem to use that. Also unsure how it interacts with nginx.

Found the following article;

https://support.cloudflare.com/hc/en-us/articles/200170986-How-does-CloudFlare-handle-HTTP-Request-headers-

[micolous]

This would blow away any caching benefit we get out of CloudFlare, as all requests would need to hit out webserver to handle the ACLs. It may be better to have a placeholder site which switches between the two, and configure the 'streaming' site as a different site in CloudFlare.

This would allow it's existing ACLs to implement it for us, without limiting access to code.timvideos.us.

I'm not how this would extend to a static files implementation of the streaming platform.

The other other alternative is to set this up so there is a static site, and the dynamic bits talk to a backend to get the list of available streams. We apply the ACLs at this level, such that the majority of content can still be cached, and only a little bit of data needs to be passed dynamically.