#36000: Update default from http to https in urlize when protocol not provided
--------------------------------------+------------------------------------
Reporter: Saravana | Owner: Saravana
Type: Cleanup/optimization | Status: assigned
Component: Template system | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Adam Johnson):
I think we can use a plan similar to how #34380 shook out, with a plan
like:
1. Introduce a transitional setting (`URLIZE_ASSUME_HTTPS`) that defaults
to `False`. This goes on the deprecation plan for removal in N+2 versions.
2. When the
[https://github.com/django/django/blob/40d5516385448a73426aad396778f369a363eda9/django/utils/html.py#L353
responsible code path is hit] (which should be fairly rare as it only
applies to
[https://github.com/django/django/blob/40d5516385448a73426aad396778f369a363eda9/django/utils/html.py#L299-L301
limited domains]), check the setting. If it’s `False`, warn and use
'http', otherwise use 'https'.
--
Ticket URL: <https://code.djangoproject.com/ticket/36000#comment:4>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701943bbd8471-80d395ad-036e-41c2-9f3e-e622335bb66e-000000%40eu-central-1.amazonses.com.
