Skip to content

Content Security Policy #10

@Phhere

Description

@Phhere

We should support the Content Security Policy so XSS issues are nearly impossible. This means that there can't be any inline < script >-Tags or eval() in JS and there will be no onclick / onchange /... attributes.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions