Implementing a proxy about snapcloud HOT 4 OPEN

It doesn’t necessarily need to be part of the cloud server, but I do think we want to manage our own CORS proxy. We need a service that isn’t just a publicly usable proxy. Those come and go far too often. And we need it to work with our list of Snap domains. My reasoning for using our cloud server was that I’m pretty sure requiring a logged in Snap! account would make it more difficult to abuse. Combined with the fact that we don’t have to maintain a separate list of allowed hosts, I think it might make sense. We could have a route /proxy that uses Lapis to check authorization and then we can either make a request in Lua, or if performance becomes a concern we could implement the proxy directly in nginx. (But I would wait to do that.) IMO, This isn’t urgent, though EDC is constantly running into problems with their internet lab. I would like to mostly explore what it would take for us to run our own proxy and then if we think it’s feasible, then we can prioritize development later on.