On Aug 14, 5:29 pm, Dan Watson <[EMAIL PROTECTED]> wrote: > As mentioned a few times in #2070, uploaded files large enough to be > streamed to a temporary file get created with a mode of 0600, as per > python's tempfile.mkstemp. This causes two problems: > > 1. Files uploaded into memory and saved to disk respect the umask, so > uploads could have different permissions based on how big they are. > > 2. If the webserver user and django user do not match (such as when > running an external FastCGI process), the webserver can no longer > serve uploaded files. > > I got around this issue by subclassing FileSystemStorage._save to call > os.chmod, but it seems there should either be a setting (eg: > FILE_UPLOAD_MODE), or a mode that respects the current umask should be > specified when saving (and moving) the files. I can create a ticket > and patch either way.
This inconsistency seems like a bug to me, so I've created ticket #8454 [1] with a patch that implements a FILE_UPLOAD_PERMISSIONS setting, and marked it as 1.0. This seemed like the least intrusive way to go, and the default behavior is unchanged. Regards, Dan [1] http://code.djangoproject.com/ticket/8454 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
