#24459: Add option to `build_absolute_uri` to build specific http or https URI
-------------------------------------+-------------------------------------
Reporter: Rik | Owner: nobody
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: build_absolute_uri | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Chris, I believe that this [https://forum.djangoproject.com/t/do-we-need-
an-easier-toggle-for-request-is-secure-to-be-true/20751/1 forum post from
Carlton] could help with this issue. The post is about something slightly
different, but in there they link to [https://noumenal.es/notes/til/django
/csrf-trusted-origins/ another post] where they talk about a analogous
scenario (doing SSL termination separately from your app servers and
dealing with `request.is_secure()` returning `False`) which I think
relates to how Django decides whether to use `http` or `https`.
--
Ticket URL: <https://code.djangoproject.com/ticket/24459#comment:5>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701882f08d219-de2a0f14-56bc-423e-af2e-4342f5bbb2b3-000000%40eu-central-1.amazonses.com.
