3 ms·
> not expose my site in a way that could be hacked What do you mean? XSS? SQL injection? What are you afraid would get hacked? > use cloud edge worker So you
by southerntofu 6y ago
> not expose my site in a way that could be hacked
What do you mean? XSS? SQL injection? What are you afraid would get hacked?
> use cloud edge worker
So you let a 3rd party private company interfere in serving your website? Of course we rely on third parties for some things, but that's a pretty dramatic course of action to let one of those edit your webpages on the fly.
- mjgs 6y ago> What do you mean? XSS? SQL injection? What are you afraid would get hacked? Perhaps hacked isn’t the right way to describe it. The issue is that if you setup a re-build if your static site on receipt of a mention, that means anyone on the internet can rebuild your site whenever just by creating a mention. That has the potential to take your site down because for example you might run out of build monthly minutes. There are probably other ways such a setup could be used to cause issues. > that's a pretty dramatic course of action to let one of those edit your webpages on the fly The way I have been thinking of cloud edge workers is just another place you can run some compute when you get a request. I think I can see why you might be hesitant, so you might have a valid point, I haven’t spent a huge amount of time analysing the threat vectors that are inherent with edge workers. In your opinion, why are edge workers more dangerous than the usual hosting provider that ‘interferes’ with the request by rendering and returning the page?