Content-Security-Policy: connect-src directive

The HTTP Content-Security-Policy (CSP) connect-src directive restricts the URLs which can be loaded using script interfaces. The following APIs are controlled by this directive:

Note: connect-src 'self' does not resolve to websocket schemes in all browsers, more info in this issue.

CSP version1
Directive typeFetch directive
default-src fallbackYes. If this directive is absent, the user agent will look for the default-src directive.

Syntax

http
Content-Security-Policy: connect-src 'none';
Content-Security-Policy: connect-src <source-expression-list>;

This directive may have one of the following values:

'none'

No resources of this type may be loaded. The single quotes are mandatory.

<source-expression-list>

A space-separated list of source expression values. Resources of this type may be loaded if they match any of the given source expressions. For this directive, the following source expression values are applicable:

Examples

undefined

Violation cases

Given this CSP header:

http
Content-Security-Policy: connect-src https://example.com/

The following connections are blocked and won't load:

html
<a ping="https://not-example.com" href="/">Link</a>
<script>
  const response = fetch("https://not-example.com/");

  const xhr = new XMLHttpRequest();
  xhr.open("GET", "https://not-example.com/");
  xhr.send();

  const ws = new WebSocket("wss://not-example.com/");

  const es = new EventSource("https://not-example.com/");

  navigator.sendBeacon("https://not-example.com/", {/* … */});
</script>

Specifications

See also