# Google Chrome

Using a Web Browser is the easiest way to [profile web applications](../../profiling-cookbooks/profiling-http-via-browser). Blackfire supports Google Chrome and [Firefox](firefox).

## Installing the Chrome Extension

## Upgrading the Extension

The Google Chrome extension should be automatically updated by the Google Chrome Scheduler. However, if a new version is available and your browser doesn't update it, please follow these steps to force the update:

- Open `chrome://extensions` in a new browser tab;
- Check the **Developer mode** at the top right of the screen;
- Click the **Update extensions now** button.

## Content Security Policy

The browser extension injects a toolbar in the profiled webpage and uses an `<iframe>` to communicate with the probe.

In case the web page declares a [Content Security Policy](https://en.wikipedia.org/wiki/Content_Security_Policy) regarding frames usages, the communication may be broken and you would be informed in the toolbar.

In this case, you can declare Blackfire domain as trusted by adding the `blackfire.io` domain in your application's headers:

```text
Content-Security-Policy: frame-src 'self' blackfire.io
```

## Known limitations

> **Warning**
>
> The "[Profile all requests](../../profiling-cookbooks/profiling-http-via-browser#profiling-all-requests)" feature is currently not available on Chrome as the features conflicts with Chrome manifest most recent version (v3).

Whenever the feature is activated, the browser extension triggers profiling by adding a specific header to all XHR requests, which Chrome manifest v3 prohibits.

Consider using the [Firefox browser extension](firefox)to benefit from the "[Profile all requests](../../profiling-cookbooks/profiling-http-via-browser#profiling-all-requests)" feature.
