Hi, Ticket: https://code.djangoproject.com/ticket/25328
I made a proposal to include a LiveServerTestCase, which runs an HTTPS server instead of standard HTTP server. I've been asked to get more feedback for this idea. If my refactor is merged I can release the test case as a separate app. But including it in Django itself would encourage to write HTTPS-only applications and to write Selenium tests for them. I've seen recent moves to encourage various security "good habits" into Django, like integrating "security header" in 1.8 (https://docs.djangoproject.com/en/1.8/ref/middleware/#module-django.middleware.security). Let's Enrypt (which should be released in November) will futher ease enabling HTTPS. Testing HTTPS-enabled site in Django should be just as easy as testing a standard HTTP site. Do you think it's a good idea to add it to Django core? Or should I release it as as a separate app? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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/1013b9bb-a790-4d97-a6dc-4d2b719a4a79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
