Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • If you're serving the content /on/ html pages to the authenticated users i think it would come down to checking referrer tags to make sure requests are coming from your site. There's probably more subtleties to it but from what i understand this is the foundation of all anti-hotlinking systems out there…probably? Commented Mar 17, 2017 at 8:36
  • You can store the files in a folder that's not readable through the browser, or in the database, and use a route to return a blob with a content type after it has authorized the user. This probably isn't very efficient compared to serving from disk, but it's a pretty surefire way of controlling permissions. Commented Mar 17, 2017 at 9:29