HN Showcase
Back to browse
A Browser Extension for Testing Content Security Policy

A Browser Extension for Testing Content Security Policy

by bootbloopers·Apr 21, 2026·3 points·1 comment
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemSlickNiche Gem

Header override mode beats DevTools for testing strict CSP policies before deployment.

Strengths
  • •Two-mode approach: meta tag injection for quick edits, declarativeNetRequest for full header replacement.
  • •Real-time violation tracking surfaces blocked URIs and violated directives as they happen.
  • •Named configurations with URL patterns let you switch policies per environment instantly.
Weaknesses
  • •CSP debugging is narrow — many developers rarely touch CSP after initial setup.
  • •Browser DevTools already show CSP violations, just less conveniently for iterative testing.
Category
Security
Target Audience

Web developers and security engineers implementing Content Security Policy

Similar To

Report URI · Google CSP Evaluator · Browser DevTools Security Panel

Post Description

One of the things I struggled with a lot when doing web development was developing effective CSP directives, so I built a browser extension for Chrome and Firefox to assist in this task.

Similar Projects