Skip to content

CSP Improvements #37238

@silverwind

Description

@silverwind

82bfde2 added basic CSP, and I see some possible future improvements:

  1. Currently it is a <meta> tag which has some limitations compared to a HTTP header which supports the full CSP feature set. According to this, some features do not work, specifically framing protections, sandboxing, or a CSP violation logging endpoint. Meta-tag has one distinct advantage though: When a header is also present, the browser will merge the directives from both sources, which could be desirable.
  2. Currently resources are allowed from * which means no restrictions. self would be desireable for improved security but it needs to be either opt-in or opt-out so users can still load resources from other origins like external render scripts and such.

Metadata

Metadata

Assignees

No one assigned

    Labels

    topic/securitySomething leaks user information or is otherwise vulnerable. Should be fixed!type/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions