Martijn,

I think I'm trying to be a bit too clever.
Perhaps the easy way is to
1) prohibit directory listings of the web root
2) create a unique directory in the root
3) put the files in the unique dir
4) allow the user to d/l from that dir
5) clean up the directory afterwards

The way I was thinking of was some sort of serve_file plugin hack which 
would be a bit
like you described below. It's just the last line that is a tad 
difficult (this is ax2)
> Note sure if this would work but how about creating a unique hash for
> every time a user requests a file, store the hash+file+user+date/time
> information in a database and for eqvery request to /file?hash=[hash]
> let AxKit send the corresponding file from /mnt/foo/bar to the
> browser?
>
> Martijn.
>
>
>
> On 7/14/08, roseyaxkit.20.ftumsh [at] spamgourmet.com
> <roseyaxkit.20.ftumsh [at] spamgourmet.com> wrote:
>   
>> Anyone got any ideas as to a way to do this please?
>>
>> -------- Original Message --------
>> Subject: Ax2: File downloads
>> Date: Mon, 7 Jul 2008 23:13:14 +0100 (BST)
>> From: roseyaxkit.20.ftumsh [at] spamgourmet.com
>> To: axkit-users [at] axkit.org
>>
>> Lo,
>>
>> I'm trying to create links to text files on my system. What I'm trying
to
>> do is get it so that the user can do a "save link as" and save the files
>> locally.
>>
>> The files are on an nfs mount. /mnt/foo/bar. What's the best way to do
it?
>> I think a way is to create a temp directory in my webroot and move the
>> files to it. (This I can do) But it seems a bit of a hack and will
>> generate quite a lot of noise in the webroot dir.
>>
>> So, any ideas?
>>
>> Ta
>>
>> John