#33803: Add crossorigin attribute to django admin templates
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
fcrozatier |
Type: Bug | Status: new
Component: | Version: 4.0
contrib.admin |
Severity: Normal | Keywords: crossorigin COEP
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
When we store our static files on a cloud (digitalocean Spaces in my case)
and we have Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy
headers on the loadbalancer the files are blocked since they are not same-
origin. This is usually not a problem we just have to add a crossorigin
attribute, but in the case of django admin files the templates do not set
them.
Should we add the ''crossorigin'' attribute to the **script**, **link**
and **img** tags of the template files ?
Without this attribute the files are blocked with Cross-Origin Opener
Policy.
--
Ticket URL: <https://code.djangoproject.com/ticket/33803>
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/010701819191add9-43b51a4e-8a08-4a79-a329-1bc4f10f9928-000000%40eu-central-1.amazonses.com.
