Review 12.4 Merged

88033[BUGFIX] Allow site-specific Content-Security-Policy endpoints

Oliver Hader CR +2 V +2 Hard +232 −24 updated 02/05/25, 13:23

Commit message

This change allows to disable the local Content-Security-Policy
reporting endpoint by setting the global scope-specific setting
`contentSecurityPolicyReportingUrl` to zero ('0'):

* [TYPO3_CONF_VARS][FE][contentSecurityPolicyReportingUrl] = '0'
* [TYPO3_CONF_VARS][BE][contentSecurityPolicyReportingUrl] = '0'

The reporting URL now can be defined per site via csp.yaml like this:

enforce:
  inheritDefault: true
  mutations: {}
  # for disabling the reporting endpoint for a particular site
  reportingUrl: false
  # for using a different external reporting endpoint
  reportingUrl: https://reporting.example.org/
  # for using the default local reporting endpoint (default)
  reportingUrl: true

Site-specific `reportingUrl` take precedence over global settings.
In case the explicitly disabled endpoint still would be called, the
server-side process responds with a 403 HTTP error message.

Review

  • Code review CR +2 Done
    • Oliver Hader +2
  • Verified V +2 Done
    • Oliver Hader +2
    • core-ci +1 CI

Issues 1

Files 12

Review log 34

  1. Oliver Hader uploaded patch set 1 02/05/25, 12:55

  2. core-ci voted on patch set 1 V +1 02/05/25, 13:04 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/73582

  3. Oliver Hader voted on patch set 1 CR +2 V +2 02/05/25, 13:22

  4. Oliver Hader merged patch set 2 02/05/25, 13:23