On Sun, Apr 13, 2014 at 11:30 PM, <m...@pdx.edu> wrote: > Is the Django community interested in supporting HTTP range requests in > django.views.static.serve<https://github.com/django/django/blob/master/django/views/static.py> > ? >
I definitely support this. I've gotten bitten several times by the development server not supporting Range headers, and it's the kind of a problem that is quite hard to debug. I recall it took me about an hour to determine why audio wasn't seeking properly when it was being served by the development server. To Russ' point about not using the server in production: we can support Range without sacrificing our "don't use this in production" goal. Let's treat our users like consenting adults. We should definitely discourage people from using the development server in production, but not to the point where we're neutering the server, making development more difficult. Long story short: go ahead and implement that robust support, with tests, and I can take the lead on reviewing the patch. Email me offlist when it's ready, if you could, so I don't lose track of it. Thanks for bringing this up! Adrian -- 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/CABm4ZCT21JdVLfrZ9kaDYZ8X%2B2XWNtFPJPWrbBDnRczpNMJJuA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
