Vinay Sajip <[EMAIL PROTECTED]> writes: > user could access the static site directly and try to guess filenames. > Also, would the static site be available to crawlers? The only sure- > fire way of providing security would seem to be to accept the cost of > handling the image I/O on the Django site.
lighttpd includes two modules to handle such situations (mod_trigger_b4_dl and mod_secdownload). With Apache I did this using a solution with mod_rewrite and an external rewriting program (checking a time limited permission in the database). Regards, Frank --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
