Hi, I think the same in the case of:
> > 1. It would make data less portable between development (where SSL is > often not in use) and production. > > So maybe a settings option could work. El miércoles, 13 de enero de 2016, 14:21:14 (UTC+1), Eric Rouleau escribió: > > Hi > > I've created a ticket to propose adding a preferred/default protocol in > the "sites" framework at https://code.djangoproject.com/ticket/26079 > > tim suggested I bring this to the mailing list and said the following: > > I'm not immediately convinced that a database field is the way to go for a >> couple reasons: >> >> 1. It would make data less portable between development (where SSL is >> often not in use) and production. >> 2. I'm not sure it's a common case that only some sites would use SSL >> but not others. >> >> A third-party library called django-hosts, which djangoproject.com uses, >> adds a setting called HOSTS_SCHEME >> <http://django-hosts.readthedocs.org/en/latest/#django.conf.settings.HOST_SCHEME> >> to >> solve this. I think there's been some discussion about merging at least >> parts of this library into core since it solves common problems. >> >> See also #10944 <https://code.djangoproject.com/ticket/10944> (we might >> close this ticket as a duplicate of that one) and #23829 >> <https://code.djangoproject.com/ticket/23829> (about customizing >> ping_google to allow https). I think the best course of action would be >> to consider this feedback and write to the DevelopersMailingList >> <https://code.djangoproject.com/wiki/DevelopersMailingList> with your >> proposal. Either solution of a new setting or a new database field need >> feedback from a wider audience. Thanks! >> > > - actually I would say it is even more portable as you > would probably use different databases between dev and prod , meaning you > can have http in dev but https in prod > - its not just for SSL but also maybe a it could be used with other > protocols/schemes such as dav, webcal, feed > - third party libraries could now have a definitive way of generating > a full URL > > what do you guys think? > > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7063ff52-e065-4193-b615-f70c5cf45f1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
