The argument that adding LiveServerTestCase with HTTPS as a separate tool
is easy - it is valid in this case, after my refactor has been merged.
The real use-case when I (and someone else may) need
HTTPSLiveServerTestCase is the one I wrote before:
- in a HTTPS-only application you can use c
Hi,
On Monday 31 August 2015 21:24:53 Tim Graham wrote:
> however, there was previous discussion about adding SSL support to
> runserver met with mixed reaction [1] and it seems a little funny to me
> that we'd including a test SSL server and not a runserver solution.
>
> [1]
> https://groups.goo
Could you explain what types of tests require https (or otherwise expand on
the rationale for adding this)? If the answer is that we don't want to have
a separate "test settings" with all the SSL settings disabled
(CSRF_COOKIE_SECURE, SECURE_HSTS_SECONDS, etc.) then I understand this,
however,
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
