3 ms·
Images are like any other web asset and can be protected either by the web server (htpasswd) or the application's logic. I think you've been brainwashed by mod
by tredre3 3y ago
Images are like any other web asset and can be protected either by the web server (htpasswd) or the application's logic.
I think you've been brainwashed by modern storage services (S3) where the URL is essentially always public and out of your control. It's trivial to password protect an image when it's on your server. I would assume any medical provider would protect their images by checking the session and not serve them via AWS.
- trompetenaccoun 3y agoYou're right, although I would not assume anything when it comes to privacy, there are so many examples where companies did not follow best practice. We need to move away from this model where others are in control of our private data to one where it's owned and controlled by us, giving access to service providers as needed.
- gloosx 3y agoGenerally, no-one hosts public content on the S3. It is simply really expensive when it comes to outbound traffic. The content is usually cached and served by CDN, where you have full control over authentication and cross-origin rules.