[Seaside] Making a download page

Ricardo Jacas ricardo.jacas at gmail.com
Thu Mar 10 17:29:30 UTC 2011

i just dropped my code and used the function John said, but as AA says
the file is represented as a MultiByteFileStream not a WAFile...any
thoughts on how to work with that? or even make it a WAFile?

2011/3/10 AA <aa at serendip.demon.co.uk>:
> Hi Avi
> The path is accessible, and absolute.  I studied the nginx wiki very carefully, too.  It's an odd problem, because it WAS working properly in the past...
> I only noted the MultiByteFileStream because that's the file object when it's saved to the native filesystem; it's different from uploading a file to the image (which is what WAUploadFunctionalTest does).
> On Thu, 10 Mar 2011 10:46:33 +0200
> Avi Shefi <avishefi at gmail.com> wrote:
>> Amir,
>> The path to the file should be:
>> (a) accessible to the image you're running, and of course allowed by its
>> file permissions.
>> (b) generally an absolute path, however your nginx configuration might need
>> a tweak to set this up. Maybe you're missing something that nginx requires?
>> take a look: http://wiki.nginx.org/XSendfile
>> Additionally, I don't understand why you're passing a MultiByteFileStream if
>> all you need is the path to the file.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

lets reign all together

More information about the seaside mailing list