#18942: Documentation of `{% get_static_prefix %}` unclear
--------------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.staticfiles | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by aaugustin):
Serving a website with the same settings on HTTP and HTTPS isn't a problem
for static files, just use a protocol-relative `STATIC_URL` eg. `'//my-
static-files.com/'`. (It may be a bad idea for other reasons, for instance
you're sharing the session cookie between HTTP and HTTPS, which isn't
great for security.)
I'm going to be blunt -- saying that "all that static stuff needs
rethinking" doesn't help, besides pissing of the (smart) people who put a
lot of time and effort into implementing it. If you believe that "all this
applies to media files as well", quite obviously, you haven't understood
the goals and the use case of the staticfiles application.
You're welcome to contribute on this topic, but please take the time to
study and understand the existing features before dismissing them, and
take into account backwards-compatibility and history.
----
So let's keep this ticket on topic. It's specifically about recommending
`{% static %}` in the docs, explaining why `{% get_static_prefix %}`
exists, and (maybe) deprecating it. Actually there isn't a lot of value in
this deprecation; we could just leave it for people who happily use it,
but discourage its use in the documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/18942#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
