-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-09-24 22:53, J Y wrote: > Are there any obvious solutions that I have over looked? Or am I > stuck having to use django to serve the files?
If you have deployed through mod_wsgi: Just serve the files through Apache but restrict access by having Apache query the Django user database: https://docs.djangoproject.com/en/1.5/howto/deployment/wsgi/apache-auth/ This will allow you to use HTTP basic auth when a user wants to access a file in a protected location. Although it will not limit the user's access to only the files he/she uploaded, meaning that any authenticated user can access ALL protected files. HTH, - -- Michael Fladischer Fladi.at -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQIcBAEBAgAGBQJSQo0JAAoJEGlMre9Rx7W2s7AQAJ/T70od7W/8PzmImAJzS1G5 yH2flMjwnPf7GVhlhElot1QxMuHp99O+29/+sEEgMxhsAh6tBr770U+JfNic5/YL xhKwYS82GhzoPhgr2p9O3Zmm3pDzmCB7w+Y1omjPH2JhWWARdja/4mZmM/nU53Wq HhYcre+po4TyjY86/6y4/c6RQm3QUea7Jo5O6DDcd8byCAmD8U7Tt0ObypVHaUE+ EZc14Gh95ZWSsfmXKeK3xJ7LKvrasOpKhqy9a0HRoHExpoqw9BYIgGwtqhn3Alx8 MI4DoNwpQWm3PCtgRq3hqfsRDnOvisUJmdKtNDUSE8H23T5DohVXVHeUzpnkp+zq JgdqxEUYGCHe6al2sonI/cfeKlzDtjNm0qTJGsuABHwg0snj/lp63LHJpL+yEsTa EAdSdQHPV1BX1nXZeRzsKffIQ6r84HcWGtUn7l/VCzCyZA+QHDMsNR/dL8oAH3Oe q80qIRM3IopuP/4px00Qa5owcOQaus8MZUxXZ3IvxQcycxec4TmMAp/f6KIisT3c 3MOLgx5K6NOt1FuzQtoAAOgyJKz28YTjIInZ2yq13CypYqp1U6LdCoqGNf5C/58z tzR8/yExI1Cc/1hMS1wFvE5apUPkTB/PglYWaNXLdnuWtZ44kXgsMR84ivYSRSmI W5kZHsT1jXKR+Tbg2ySH =tuRc -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
