Django: Serving a Download in a Generic View

Why do you want to do this with a generic view? It's very easy to do this without generic views:

from django.http import HttpResponsedef song_download(request, song_id):    song = Song.objects.get(id=song_id)    fsock = open('/path/to/file.mp3', 'rb')    response = HttpResponse(fsock, content_type='audio/mpeg')    response['Content-Disposition'] = "attachment; filename=%s - %s.mp3" % \                                     (song.artist, song.title)    return response

I'm not sure if it's possible to make this work somehow with a generic view. But either way, using one is redundant here. With no template to render, the context that is automatically provided by the generic view is useless.

To wrap my comment to Tomasz Zielinski into a real answer:

For several reasons it is indeed better to let apache/nginx/etc do the work of sending files. Most servers have mechanisms to help in that usecase: Apache and lighttpd have xsendfile, nginx has X-Accel-Redirect.

The idea is that you can use all the features of django like nice urls, authentification methods, etc, but let the server do the work of serving files. What your django view has to do, is to return a response with a special header. The server will then replace the response with the actual file.

Example for apache:

def song_download(request):    path = '/path/to/file.mp3'    response = HttpResponse()    response['X-Sendfile'] = smart_str(path)    response['Content-Type'] = "audio/mpeg"    response['Content-Length'] = os.stat(path).st_size    return response

• install mode_xsendfile
• add XSendFileOn on and (depending on the version) XSendFileAllowAbove on or XSendFilePath the/path/to/serve/from to your apache configuration.

This way you don't reveale the file location, and keep all the url management in django.

Serving static files with Django is a bad idea, use Apache, nginx etc.

https://docs.djangoproject.com/en/dev/howto/static-files/deployment/