#34380: Make URLField assume "https".
-------------------------------------+-------------------------------------
Reporter: Coen van der Kamp | Owner: Coen van
Type: | der Kamp
Cleanup/optimization | Status: closed
Component: Forms | Version: 4.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
> Or is the way to go to use `FORMS_URLFIELD_ASSUME_HTTPS` for now,
ignoring its `DeprecationMessage`, and to remove the setting with Django
6.0 again?
That was our idea (check out the entire [https://forum.djangoproject.com/t
/stop-the-django-5-0-press-move-urlfield-assume-scheme-change-from-
deprecation-to-hard-cut/25652/20 discussion]). If you agree for an early
adoption of the new (Django 6.0+) default, set
`FORMS_URLFIELD_ASSUME_HTTPS = True` and ignore it's deprecation warning
during Django 5.X release cycle with e.g.
`warnings.filterwarnings("ignore", "FORMS_URLFIELD_ASSUME_HTTPS",
category=RemovedInDjango60Warning)`. In Django 6.0 you will be able to
remove both the `FORMS_URLFIELD_ASSUME_HTTPS` setting and a `warnings`
filter.
--
Ticket URL: <https://code.djangoproject.com/ticket/34380#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d1c81a8a6-de56eb22-2d10-47c5-81d5-026ff23fbc12-000000%40eu-central-1.amazonses.com.
