Anyone know how portable "symlink" is for Windows NT with IIS?
The purpose of this is to allow the viewing of protected images by creating a complex symlink name pointing to a secure file on the server on a per-user/per-browse basis (on the fly).
With this method, I won't have to pipe the image through a cgi every time the image is required - a cgi for something like this causes too much load - and still keep a fair level of security.
But the question of course, is can I do it?
The purpose of this is to allow the viewing of protected images by creating a complex symlink name pointing to a secure file on the server on a per-user/per-browse basis (on the fly).
With this method, I won't have to pipe the image through a cgi every time the image is required - a cgi for something like this causes too much load - and still keep a fair level of security.
But the question of course, is can I do it?