4 ms·

Thanks grapehut. * No excuses, the website settings look like shit and will be fixed. * You can add subdomains that point to the same site. (For example, www.

by nubela 11y ago

Thanks grapehut. * No excuses, the website settings look like shit and will be fixed. * You can add subdomains that point to the same site. (For example, www.example.com and example.com). If you have a different site, you can add a new one in the top right corner. (For example, 2 different websites of "test.com" and "dashboard.test.com") * On the SSL cert issue, Sorry about this, this is a bug. Our engineers are looking into it. Do you have an email that I can contact you with? You can email us at hello@kloudsec.com and our engineers will immediately help you with this. * We have no content policy as of now. (This is a schlep and we'll fix this. We'll send an email update once we have this) * Caching is based on file hashing. Not filenames. You can also manually clear the CDN cache from the dashboard itself. * DDoS defense. Erm well, we're just lacking 1 last step. Having enough traction/capital to buy lots of bandwidth from our DC to stomach it. We're on it. Thanks for this feedback. This is insanely useful. We're very excited about this space.

grapehut 11y ago
> Caching is based on file hashing. Not filenames. I'm not really sure what this means, and I've used all the major CDNs/reverse proxies =) Cloudflare for instance is generally controlled by the filetypes, while cloudfront is generally controlled by the cache control headers sent by the origin server. Either way, I think exactly how it works needs to go into its own fully-fledged article. It's probably the most important thing a reverse-proxy does, and should be documented very clearly. BTW one unique feature of cloudfront you might want to support, is setting cache control with vary on cookie. So with cloudfront, I can make non-logged in users see a cached page, while logged-in users see a non-cached page. It allows me to take a huge amount of load off the origin server, with no real downsides (in my case).
- nickpsecurity 11y ago
  My guess is it's a de-duplication trick. They might even have dedicated caching servers. I'd guess others might do it behind the scenes with them just being upfront about it for whatever reason. Just an educated guess.

by nubela 11y ago

grapehut 11y ago

> Caching is based on file hashing. Not filenames. I'm not really sure what this means, and I've used all the major CDNs/reverse proxies =) Cloudflare for instance is generally controlled by the filetypes, while cloudfront is generally controlled by the cache control headers sent by the origin server. Either way, I think exactly how it works needs to go into its own fully-fledged article. It's probably the most important thing a reverse-proxy does, and should be documented very clearly. BTW one unique feature of cloudfront you might want to support, is setting cache control with vary on cookie. So with cloudfront, I can make non-logged in users see a cached page, while logged-in users see a non-cached page. It allows me to take a huge amount of load off the origin server, with no real downsides (in my case).

nickpsecurity 11y ago
My guess is it's a de-duplication trick. They might even have dedicated caching servers. I'd guess others might do it behind the scenes with them just being upfront about it for whatever reason. Just an educated guess.