3aee641c3d
🤖 I have created a release *beep* *boop* --- ## [18.1.0](https://github.com/puppeteer/puppeteer/compare/v18.0.5...v18.1.0) (2022-10-05) ### Features * **chromium:** roll to Chromium 107.0.5296.0 (r1045629) ([#9039](https://github.com/puppeteer/puppeteer/issues/9039)) ([022fbde](022fbde85e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
30 lines
696 B
Markdown
30 lines
696 B
Markdown
---
|
|
sidebar_label: Page.setBypassCSP
|
|
---
|
|
|
|
# Page.setBypassCSP() method
|
|
|
|
Toggles bypassing page's Content-Security-Policy.
|
|
|
|
**Signature:**
|
|
|
|
```typescript
|
|
class Page {
|
|
setBypassCSP(enabled: boolean): Promise<void>;
|
|
}
|
|
```
|
|
|
|
## Parameters
|
|
|
|
| Parameter | Type | Description |
|
|
| --------- | ------- | ------------------------------------------------- |
|
|
| enabled | boolean | sets bypassing of page's Content-Security-Policy. |
|
|
|
|
**Returns:**
|
|
|
|
Promise<void>
|
|
|
|
## Remarks
|
|
|
|
NOTE: CSP bypassing happens at the moment of CSP initialization rather than evaluation. Usually, this means that `page.setBypassCSP` should be called before navigating to the domain.
|