You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the removal of X-XSS-Protection, it would be nice to simplify adding Content-Security-Policy.
One way to do this is to turn on Content-Security-Policy-Report-Only by default. Spring Security could provide a simple reporting endpoint that publishes an ApplicationEvent when the policy is violated. Similar to DefaultLoginPageGeneratingFilter, this endpoint would likely be replaced, but would work for giving applications a head start on Content-Security-Policy.
Folks would change this behavior by setting the header themselves like so:
The above would replace Content-Security-Policy-Report-Only: default-src 'self'; report-uri: /report-uri with Content-Security-Policy: default-src 'self'.
Provide default endpoint for reporting violations
Change default directive for report-only to report to default endpoint
Make report-only setting the default
The text was updated successfully, but these errors were encountered:
With the removal of
X-XSS-Protection
, it would be nice to simplify addingContent-Security-Policy
.One way to do this is to turn on
Content-Security-Policy-Report-Only
by default. Spring Security could provide a simple reporting endpoint that publishes anApplicationEvent
when the policy is violated. Similar to DefaultLoginPageGeneratingFilter, this endpoint would likely be replaced, but would work for giving applications a head start onContent-Security-Policy
.Folks would change this behavior by setting the header themselves like so:
The above would replace
Content-Security-Policy-Report-Only: default-src 'self'; report-uri: /report-uri
withContent-Security-Policy: default-src 'self'
.The text was updated successfully, but these errors were encountered: