#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 Chris Spencer):
I think the response here misses the point. Yes, everyone agrees that
https should be used everywhere publicly. That's the problem. Currently,
`build_absolute_uri` does not do that. In some environments, SSL is
handled by a public facing load balancer which redirects them as non-SSL
requests to a non-public pool of servers. Those servers don't use SSL to
make request handling faster and simplify SSL certificate management, and
since they're not publicly accessible, that's fine. In that situation,
Django only see http, causing `build_absolute_uri` to only build non-SSL
URLs. Having some option to force it to use https would be more convenient
that having to do a str.replace or slice+concat to convert "http://"; to
"https://";.
--
Ticket URL: <https://code.djangoproject.com/ticket/24459#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701882c3c5907-47d7f940-532e-472b-aca8-8f3c9f005d7e-000000%40eu-central-1.amazonses.com.
