mirror of
https://github.com/puppeteer/puppeteer
synced 2024-06-14 14:02:48 +00:00
e9df6750d2
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.5.2</summary> ## [19.5.2](https://github.com/puppeteer/puppeteer/compare/puppeteer-v19.5.1...puppeteer-v19.5.2) (2023-01-11) ### Miscellaneous Chores * **puppeteer:** Synchronize puppeteer versions ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.5.1 to 19.5.2 </details> <details><summary>puppeteer-core: 19.5.2</summary> ## [19.5.2](https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v19.5.1...puppeteer-core-v19.5.2) (2023-01-11) ### Bug Fixes * make sure browser fetcher in launchers uses configuration ([#9493](https://github.com/puppeteer/puppeteer/issues/9493)) ([df55439
](df554397b5
)), closes [#9470](https://github.com/puppeteer/puppeteer/issues/9470) </details> --- 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
697 B
Markdown
30 lines
697 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.
|