Others already expressed their perplexities with this idea. Personally, I've never had to do anything like this - but I've been considering the problem of "serving" (in a loose sense) files without "exposing" them. Now, an option that occurred to me is to create a temporary symlink to the actual file with File::Temp, having a separate process removing it asynchronously after a suitable timeout. I'd like to hear more experienced programmers' opinion about this scheme...
In reply to Re: letting a browser client select a file to download by inode
by blazar
in thread letting a browser client select a file to download by inode
by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |