[Seaside] Re: Serving private static files
tulipe.moutarde at gmail.com
Sun Nov 6 20:12:14 UTC 2011
I've finally implemented a quite simple (and probably stupid) solution:
Downloadable items have a specific url: "/private-stuff/<a specific token>".
When one of those URL is hit, the session looks if the item is available
for the user and serve the file (or throw a 404).
It seems weird to me that the file is served by the session... Do you
see a cleaner solution ?
On 23/10/11 12:53, Francois Stephany wrote:
> Hi list,
> I want to serve private static file from disk with Seaside. By private,
> I mean that only logged-in users can access those files. Users would
> only see the files they have the permission to see/download.
> What's the best solution to achieve this ? I see two directions:
> - embed something like WAExternalFileLibrary, access the session and
> serving the files through Seaside.
> - store the files on S3 and generate an url with a token, only active
> during a given amount of time. The files would be in a private bucket.
> Have you ever encountered that use case ? What would you recommend ?
More information about the seaside