#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 Daniel Hahler):
There is no (easy) way to pass/use `assume_scheme` via
`django.db.models.fields.URLField` (directly), avoiding the deprecation
messages (since using the transitional setting
`FORMS_URLFIELD_ASSUME_HTTPS` also triggers a deprecation message
already).
Should `django.db.models.fields.URLField` accept/handle `assume_scheme`?
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?
Might be nice to document this then in the release notes / documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/34380#comment:11>
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/0107018d1c718d68-15fb53a1-06db-4666-a29b-baf229087c64-000000%40eu-central-1.amazonses.com.
