#27590: Prevent public access of staticfiles manifest
--------------------------------------+------------------------------------
Reporter: David Sanders | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.staticfiles | Version: 1.10
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 Kevin Christopher Henry):
At #28764 I reached a similar conclusion for very different reasons.
I don't see much point in making the location configurable, though. It
seems to me that the file should just be stored to some standard location
within the codebase. The obvious analogy here would be to
`makemigrations`, which does the same thing. As I argue in the other
ticket, this is a configuration file that affects Django's behavior, is
tied to a specific commit, and has nothing to do with the actual serving
of static files. Storing it in the codebase would solve David's issues
above, would solve the correctness and performance issues I mentioned, and
would do so for all users without any new settings. Are there advantages
to storing the file in an external location that I've overlooked?
--
Ticket URL: <https://code.djangoproject.com/ticket/27590#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.48b601fecca1982ee24b1dfa655e34f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
