Re: [Django] #25921: Make runserver handle HTTPS requests.

[Django]

#25921: Make runserver handle HTTPS requests.
-+-
 Reporter:  azmeuk   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  runserver, ssl,  | Triage Stage:
  https  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 This was previously proposed on [https://groups.google.com/d/topic/django-
 developers/PgBcSEiUdw0/discussion django-developers] and declined in favor
 of other options.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.574e74fed9b80c6f9ef1f82f65460be4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25921: Make runserver handle HTTPS requests.

[Django]

#25921: Make runserver handle HTTPS requests.
-+-
 Reporter:  azmeuk   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  runserver, ssl,  | Triage Stage:
  https  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by azmeuk):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> Hi. The builtin '''manage.py check --deploy''' encourages to enable all
> the available securities, including SECURE_SSL_REDIRECT that actually
> redirect any non HTTP request to a HTTPS request. However '''manage.py
> runserver''' does not allow HTTPS request. It is too bad that we cannot
> test all the available options in development before we deploy an app.
>
> The existing [https://github.com/teddziuba/django-sslserver django-
> sslserver] solves the issue, quite simply. But on the other hand,
> '''manage.py runsslserver''' does not allow simple HTTP request.
>
> I think this would be a good idea to enhance the current runsslserver
> with what we can find in django-sslserver, so in the end it can handle
> both HTTP and HTTPS requests.
>
> I am OK to make a merge request if you are interested.

New description:

 Hi. The builtin '''manage.py check --deploy''' encourages to enable all
 the available securities, including SECURE_SSL_REDIRECT that actually
 redirect any non HTTP request to a HTTPS request. However '''manage.py
 runserver''' does not allow HTTPS requests. It is too bad that we cannot
 test all the available options in development before we deploy an app.

 The existing [https://github.com/teddziuba/django-sslserver django-
 sslserver] solves the issue, quite simply. But on the other hand,
 '''manage.py runsslserver''' does not allow simple HTTP request.

 I think this would be a good idea to enhance the current runsslserver with
 what we can find in django-sslserver, so in the end it can handle both
 HTTP and HTTPS requests.

 I am OK to make a merge request if you are interested.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e87019c295568b32f39a7f017799328b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25921: Make runserver handle HTTPS requests.

[Django]

#25921: Make runserver handle HTTPS requests.
---+---
 Reporter:  azmeuk |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  HTTP handling  |Version:  master
 Severity:  Normal |   Keywords:  runserver, ssl, https
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 Hi. The builtin '''manage.py check --deploy''' encourages to enable all
 the available securities, including SECURE_SSL_REDIRECT that actually
 redirect any non HTTP request to a HTTPS request. However '''manage.py
 runserver''' does not allow HTTPS request. It is too bad that we cannot
 test all the available options in development before we deploy an app.

 The existing [https://github.com/teddziuba/django-sslserver django-
 sslserver] solves the issue, quite simply. But on the other hand,
 '''manage.py runsslserver''' does not allow simple HTTP request.

 I think this would be a good idea to enhance the current runsslserver with
 what we can find in django-sslserver, so in the end it can handle both
 HTTP and HTTPS requests.

 I am OK to make a merge request if you are interested.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.e324e3c32e4f290b026e848a98676918%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.