{{define "title"}}CSP reports · MeshTender{{end}} {{define "header"}}
| Directive | Blocked | Page | Reports | Last seen |
|---|---|---|---|---|
| {{.Directive}} {{if eq .Disposition "report"}} report-only {{end}} {{if and $.ShowAll (eq .Source "extension")}} extension {{end}} | {{.BlockedURI}} |
{{.Host}}{{.DocumentPath}}{{if .LineNumber}}:{{.LineNumber}}{{end}}
{{/* Name the injector when the report identified one — it's the evidence
for the “extension” label, and browsers report only the scheme (no
extension ID), so there's nothing identifying to leak here. */}}
{{if and .SourceFile (ne .Source "page")}}
injected by
{{end}}
{{if .Sample}}{{.SourceFile}}{{.Sample}} {{end}}
|
{{.Hits}} |
{{ts .LastSeen "datetime"}}
first {{ts .FirstSeen "date"}}
|
{{if eq .Source "page"}} No violations reported. That's the result you want: it means nothing on the site is being blocked by the Content Security Policy. {{else}} Nothing recorded. {{end}}
Violations caused by browser extensions injecting into a visitor's page. Nothing here is a bug in MeshTender and none of it is fixable from our side — it's kept only so an extension can be recognized as the cause rather than mistaken for an app problem. Note that an extension injecting an inline script is indistinguishable from a genuine inline-script violation, so those are listed under “Page”.
{{end}}