#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
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Comment:
Florian says,
I think we should just bite the dust and add a setting which the static
manifest gets written to (directly, without involving storage). Moving
this file out of `STATIC_ROOT` is the only sensible solution I see.
`S3BotoStorage` should redirect the manifest to a different (secure)
bucket if needed. Maybe we can make it easier to detect that this file is
"sensitive".
--
Ticket URL: <https://code.djangoproject.com/ticket/27590#comment:1>
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.30a5e8dac5549a181a5c86ec9193ea5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.