On Mon, Apr 14, 2014 at 11:30 AM, <m...@pdx.edu> wrote: > Is the Django community interested in supporting HTTP range requests in > django.views.static.serve? > > The primary benefit I see is that it makes files served up for <video> and > <audio> "seek-able" with the django server. This generally isn't a problem > for small files (except in Chrome), but becomes an issue for larger ones.
My immediate inclination is to say No - for the reason that is listed at the very top of the source file in question: https://github.com/django/django/blob/master/django/views/static.py """ These are only to be used during development, and SHOULD NOT be used in a production setting. """ One of the easiest ways to make sure that a feature isn't used in production is to ensure that it doesn't have features that would be useful in production. Supporting ranged downloads for static files strikes me as exactly that sort of feature. My opinion - If you need to test ranged downloads of static files, then fire up a real web server - like gunicorn - in your development environment. This isn't something that should be added to Django. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84-ZZw%2BNRQXY9r%2BO97O%2Bkxf%2Bh-c1ub%3DRBnFqKOtkvV2%2BgQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
