I think in those cases a small middleware would be prefered opposed to a new setting (and therefore nothing which needs to be in core). That said: how is the "cloud" telling you if the request is https or not?
Cheers, Florian On Sunday, August 20, 2017 at 7:03:08 PM UTC+2, wangwenpei wrote: > > Dear all: > > I know we have *settings.SECURE_PROXY_SSL_HEADER *to control https > header when we use load-balancer. > > but I found some small cloud platform doesn't support user set it. > > so, should we add new config option to support this case, something > like: *'SCHEMA_FORCE_HTTPS=True'?* > > I am not sure this is a feature. because it is cloud platform problem, > not Django. > > if community think can add into django. I think I can finish it. > > > > > > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/996fbf8f-00b9-4efb-8c45-ee17c9e05df5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
