AddContentSecurityPolicyEvent
extends Event
in package
Allows to inject something into the default content policy. This is for example useful when you're injecting Javascript code into a view belonging to another controller and cannot modify its Content-Security-Policy itself.
Note that the adjustment is only applied to applications that use AppFramework controllers.
WARNING: Using this API incorrectly may make the instance more insecure.
Do think twice before adding whitelisting resources. Please do also note
that it is not possible to use the disallowXYZ functions.
Tags
Table of Contents
- $policyManager : ContentSecurityPolicyManager
- __construct() : mixed
- Compatibility constructor
- addPolicy() : void
Properties
$policyManager
private
ContentSecurityPolicyManager
$policyManager
Methods
__construct()
Compatibility constructor
public
__construct(ContentSecurityPolicyManager $policyManager) : mixed
In Nextcloud 17.0.0 this event class used a now deprecated/removed Symfony base class that had a constructor (with default arguments). To lower the risk of a breaking change (PHP won't allow parent constructor calls if there is none), this empty constructor's only purpose is to hopefully not break existing sub- classes of this class.
Parameters
- $policyManager : ContentSecurityPolicyManager
Tags
Return values
mixed —addPolicy()
public
addPolicy(EmptyContentSecurityPolicy $csp) : void
Parameters
- $csp : EmptyContentSecurityPolicy