1 min read

Imperative Content Security Policy with Service Worker

Paul Kinlan

Paul Kinlan

Lead of Chrome DevRel

I wrote up my thoughts on detecting content injection into sites. It came down to:

  • Use HTTPS
  • Use Content Security Policy (CSP)

The issue being CSP has low adoption with a poor developer experience. It got me thinking about how it could be improved and fit into a model that I think is more amiable to most developers. A little bit of back story.

CSP is a declarative language that describes to the browser how it should manage requests made by a page to the network.

There is nothing inheritnelty wrong with this, it's just that I find the syntax hard.

Will we get imperative Content Security Policy with Service Worker for free.

Stay in the loop.

I'm trialing a newsletter. Join for monthly insights into web dev, Chrome, and the open web.

alternate_email

Get in touch

Open to chat about Chrome or Web development.

Book a consultation