[Seaside] Serving files in a quick yet secure way
tibabenfortlapalanca at gmail.com
Tue May 18 02:15:58 UTC 2010
I finally solved it by using WAFileDirectory, its usage is so simple it
didn't occur to me it could work like that!
After talking to the client it seems it's no big deal if the files can be
accessed from the browser (I thought it would be), as you would still need
to know their exact path, and these tend to be pretty cryptic in their
case... Still, if a file leaked it'd be strictly inside the organisation.
Anyway, thanks a lot for all the options, I'll consider them if I ever come
across the same problem again!
Going off-topic, I've got to say that small communities are the ones with
the best "live" support. I mean, where else do you get answers to your
particular problems from the people whose books you've been reading?
2010/5/17 Philippe Marschall <philippe.marschall at gmail.com>
> 2010/5/17 AxiNat <tibabenfortlapalanca at gmail.com>:
> > Hi all,
> > I'm coding an app that will have to deal with quite a handful of pretty
> > files in a daily basis.
> > So far, for prototyping, I've been using a WAFileLibrary, but it's
> > more and more clear to me that this is the wrong approach, because it
> > forever to add/delete a file from the library and the application will
> > to be deployed soon for real life usage.
> > The apache solution is not valid in my case, cos these files MUST be
> > inaccessible via the browser,
> Not so fast. You can put them in a folder above docroot and then use
> mod_xsendfile . That uses the sendfile() system call to let the
> kernel deliver the file. That's a about as efficient as it gets, the
> data won't even touch user space.
>  http://tn123.ath.cx/mod_xsendfile/
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside