Skip to content

csp: improve docs #12812

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Dec 1, 2025
Merged

csp: improve docs #12812

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f2192e5
csp: improve docs
ematipico Dec 1, 2025
890c5c1
feedback
ematipico Dec 1, 2025
c5a5fa6
Apply suggestions from code review
ematipico Dec 1, 2025
70b575e
apply suggestion
ematipico Dec 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 44 additions & 1 deletion src/content/docs/en/reference/experimental-flags/csp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ These properties are added to all pages and **completely override Astro's defaul
<Since v="5.9.0" />
</p>

A list of valid sources for the `script-src` and `style-src` directives.
A list of valid sources for the `script-src` and `style-src` directives, including [values for subclasses](#adding-values-for-subclasses).

The `script-src` and `style-src` directives are handled by Astro by default, and use the `'self'` resource. This means that scripts and styles can only be downloaded by the current host (usually the current website).

Expand Down Expand Up @@ -188,6 +188,49 @@ After the build, the `<meta>` element will instead apply your sources to the `st
</head>
```

### Adding values for subclasses

You can also use this field to add valid values that belong to [`script-src-attr`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/script-src-attr), [`script-src-elem`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/script-src-elem), [`style-src-attr`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/style-src-attr) and [`style-src-elem`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/style-src-elem), such as `unsafe-hashes` and `unsafe-inline`.

For example, if you have an external library that adds scripts or inline styles to some HTML elements of the page, you can add `unsafe-inline` to tell the browser that they are safe to render.

```js title="astro.config.mjs"
import { defineConfig } from 'astro/config';

export default defineConfig({
experimental: {
csp: {
styleDirective: {
resources: [
"'unsafe-inline'"
]
},
scriptDirective: {
resources: [
"'unsafe-inline'"
]
}
}
}
});
```

After the build, `style-src` and `script-src` directives will contain the `'unsafe-line'` resource:

```html
<head>
<meta
http-equiv="content-security-policy"
content="
script-src 'unsafe-line';
style-src 'unsafe-line';
"
>
</head>
```



#### `hashes`

<p>
Expand Down