Currently CloudFlare handles the choirless.com-->www.choirless.com redirect only. Is a straight "A" record pointing to CloudFoundry.
If we wanted to get CloudFlare to proxy this traffic, it would have several advantages:
- CloudFlare would handle SSL termination and certificate rotation 👍
- CloudFlare would provide DDOS protection
- CloudFlare would provide CDN-like distribution of static assets (images, css etc)
There's one important caveat: 🟥 we don't want COS traffic going through the app, because CloudFlare has limits on response size. So we'd need to:
- change the "See Latest Render" to download the video from COS directly
- change the "load leader part" + "load additional parts" during recording to download the video from COS directly
- change the "upload video" mechanism to write to COS directly
^ the above three can be achieved with "pre-signed URLS" - the app generates a pre-signed URL giving the browser permission to GET/PUT a COS object and the browser speaks to COS directly.
This is a reminder to a future selves 🤔
Currently CloudFlare handles the choirless.com-->www.choirless.com redirect only. Is a straight "A" record pointing to CloudFoundry.
If we wanted to get CloudFlare to proxy this traffic, it would have several advantages:
There's one important caveat: 🟥 we don't want COS traffic going through the app, because CloudFlare has limits on response size. So we'd need to:
^ the above three can be achieved with "pre-signed URLS" - the app generates a pre-signed URL giving the browser permission to GET/PUT a COS object and the browser speaks to COS directly.
This is a reminder to a future selves 🤔