Skip to content

Enable call stack for blocked_uri in Content Security Policy Reporting #269

@vibhasethi

Description

@vibhasethi

Cloned from https://bugs.chromium.org/p/chromium/issues/detail?id=786037

With the current implementation of CSP reporting, the blocked_uri tells the URI of the resource that was blocked from loading on a given document on which the violation occurred. However, lot of times the blocked resource might not be loaded by the document and could be loaded by another resource which is hard to determine with the current implementation and hence it does not help with identifying the caller for the blocked_uri. It would be helpful if in addition to blocked_uri, an additional attribute could be provided that gives the stack of uris that led to the calling of the bolcked_uri on the document on which the violation occurred.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions