Review main Abandoned

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

Oliver Hader CR 0 V 0 Normal +81 −21 updated 01/24/25, 10:13

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.

@todo
+ Important RST

Review

  • Code review CR 0
  • Verified V 0

Issues 1

Files 8

Review log 35

  1. Oliver Hader uploaded patch set 1 01/08/25, 14:53

  2. Oliver Hader uploaded patch set 2 01/08/25, 14:56

  3. core-ci voted on patch set 1 V -1 01/08/25, 15:03 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/72095

  4. core-ci voted on patch set 2 V -1 01/08/25, 15:07 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/72097

  5. Oliver Hader abandoned the change 01/24/25, 10:13