On Aug 20, 1:12 pm, Ceph <[EMAIL PROTECTED]> wrote: > The only other option I see to serving large files securely is > trickery using dynamically created sym links to the true static file > and then redirecting the user to those URLs and letting Apache serve > them. This isn't as secure, though, and permits multiple downloads > without them being recorded in my Django apps.
Lighttpd and nginx both have a clever way of dealing with this problem. You can store the real file somewhere that is readable by the web server but NOT exposed as a public URL. Then your Django application can (having authenticated the request) respond with a magical header which tells the nginx/lighttpd server to serve up the file from that location. Here's how to do it with nginx: http://wiki.codemongers.com/NginxXSendfile If your app is all about serving large files, it may well be worth putting it behind an nginx proxy purely to gain access to this feature. nginx is a really neat reverse proxy - I run simonwillison.net as nginx proxying through to mod_python/Apache for the dynamic pages and it's been working great for months. Hope that helps, Simon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
