1. it's not necessarily about SSL, it can be for any protocol but SITE
dependent.
2. and for the dev/prod , your data will be different anyway so you put
the preferred protocol accordingly to your setup.
3. it's only for generating full URLs, not for internal links (ex:
since no feedback has been given yet, I will add that the change is just
an addition (new feature) meaning there is no breaking of code , it just
provides a way to define a default protocol for a given SITE, and will
ultimately default to http when none is specified
--
You received this
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
>
+1 for me too
On Thursday, March 6, 2014 3:28:59 PM UTC-5, Andre Terra wrote:
>
> +1, for one simple reason: practicality beats purity.
>
>
> On Wed, Mar 5, 2014 at 10:23 AM, Daniel Ellis > wrote:
>
>> +1 - I've had the same issue with sorl thumbnail.
>>
>>
>> On Wed, Mar 5,