stable
Clone or download
request #17114: Setup cross-origin isolation when loading assets or the documentation
By itself this contribution has a limited usefulness, the main goal is to see if deploying such changes does not cause too much troubles in the the "production" environnement Tuleap is deployed into before going for a wider deployment. To test, redeploy the nginx configuration: new headers should be set on the impacted resources and everything should continue to work. If you go to the local documentation on /doc/en/ on your dev instance (you will need to install the tuleap-documentation package), the page will be shown as cross origin isolated: `self.crossOriginIsolated` will be true (you can use your browser dev tool to do that). More information about cross-origin isolation can be found here: https://web.dev/coop-coep/ https://docs.google.com/document/d/1zDlfvfTJ_9e8Jdc8ehuV4zMEu9ySMCiTGMS9y0GU92k/edit https://resourcepolicy.fyi/ Change-Id: Id5efae6c005def507195bd74bbd19cf2cd3d09d9
Modified Files
| Name | ||||
|---|---|---|---|---|
| M | src/etc/nginx/tuleap.d/03-locations.conf | +10 | −0 | Go to diff View file |