Bug #76944
closed
Subrequest-integrity should also add cross-origin header
0%
Description
In Feature #66698 the integrity-property was added to PAGE.includeJS (and similar).
However (at least with newer chrome-versions) with this the resources are not loaded anymore, because a crossorigin attribute is required together with integrity, the error-log displays:
Hacking the Pagerenderer solves this, see attached patch, which simpy adds 'crossorigin="anonymous"'. However even better would be to make that configurable.
Files
Updated by Wouter Wolters almost 8 years ago
- Status changed from New to Rejected
I close this ticket as a duplicated of #7645
Please continue there.
Updated by Mathias Brodala over 7 years ago
Wouter Wolters wrote:
I close this ticket as a duplicated of #7645
Please continue there.
Could you check that ticket number? I just created #77873 due to the same issue.
Updated by Tim Riemenschneider over 7 years ago
There seems to be a "9" missing, the ticket should be 76459 (as already mentioned above in "Related issues" ;-) )
Updated by Mathias Brodala over 7 years ago
Tim Riemenschneider wrote:
There seems to be a "9" missing, the ticket should be 76459 (as already mentioned above in "Related issues" ;-) )
Yeah, noticed that in the meantime, thanks anyways. ;-)